| 3 | The Helma NG JavaScript runtime uses the *Mozilla Rhino|http://www.mozilla.org/rhino/* JavaScript engine is based on [Mozilla Rhino][rhino] and adds a few features to it:supports |
| 4 | JavaScript 1.7 with partial support for JavaScript 1.8 features. |
| 5 | * A *module system* [rhino]: http://www.mozilla.org/rhino/ |
| 6 | * An enhanced *shell* |
| 7 | * Infrastructure for *resource* loadingTo run Helma NG, add the helma-ng/bin directory to your PATH environment |
| 8 | * Advanced Java *classpath* featuresvariable: |
| 9 | |
| 10 | export PATH=$PATH:/path/to/helma-ng/bin |
| 11 | |
| 12 | To start a shell session, just run the helma command without any arguments: |
| 13 | |
| 14 | helma |
| 15 | |
| 16 | To run a script simply pass it to helma on the command line: |
| 17 | |
| 18 | helma apps/demo/main.js |
| 19 | |
| 20 | If you run a script that is contained in Helma's module path you can also |
| 21 | use the simpler abstract module name instead of the file name. For example, |
| 22 | to run the helma test suite: |
| 23 | |
| 24 | helma test/all |
| 25 | |
| 26 | To create a new web application, use the admin/create script. This will copy |
| 27 | an simple skeleton app to the location you define. You can pass the |
| 28 | application directory as command line argument, or the script will prompt you |
| 29 | for it. |
| 30 | |
| 31 | helma admin/create [appdir] |
| 32 | |
| 33 | Run helma with the -h or --help switch to get more information about available |
| 34 | command line options. For example, the -i or --interactive option allows you |
| 35 | to run an application and use the shell at the same time, which can be really |
| 36 | handy. |
RSS feed for site updates