SPEC: NSR8: Web Commander

See the associated README.MD markdown files included with the source for more information.

There are no major code changes in NSR8. There are bug fixes, tool additions and source layout changes. It is very likely that there are code bugs spilled over from NSR7 which have not yet been discovered. Please report any issues.

SPEC: NSR7A: Web Commander

No significant source changes to the previous release.

The repository layout was modified. This release details the source reflection for the changes which were meant for NSR7 branch.

SPEC: NSR7: Web Commander

JSON, XML, Win32/64 JNA, Win32 COM/OLE JNA, Linux x86/64/ARMel/MIPSel JNA, JavaScripting, Full Java to Javascript runtime package loading support, URL Class, Jar, and Script Loading, JS Server Pages, Javascript GUI Debugging, Text Macro Shell Programming, Command Shell Programming, Rhino Android JIT, (HTTP+S)/Server & Web Browser, Server Side Template Scripting, WebServer Archive Mounting/Active Content Provider and custom mimetype driver filter-programming, with server-data-interop/internal-server-query, Runtime Package, Class, and Script Loading introspection, REQUIRE.JS SSI, SQL/Client, +Microsoft Access Database support.

AND MORE... All accessible through scripting, with developer JavaDocs for external libraries, based on a tiny in-house-core.

This release has been updated with the extended JNA library-set.

< 5MB

SPEC: NSR6: Storyteller

XML, JSON and JNA Support are optional add-ons for all configurations and platforms. When included in a class-path directory, they are automatically loaded in the runtime classpath of the nano-starbox-core.jar

Android scripting support is not optional if you want android scripting support. When this archive is in the class path of the host application, nano-starbox-core.jar will setup the environment for correct use with Mozilla Rhino JIT. The minimum size requirement for an android release is 2.2 MB.

Rhino Console and Rhino Console Debug are optional desktop features.

Voyager is an optional desktop feature.

This specification does not necessarily detail the API, only the project structure, with a working theory.

SPEC: NSR5

XML, JSON and JNA Support are optional add-ons for all configurations and platforms. When included in a class-path directory, they are automatically loaded in the runtime classpath of the nano-starbox-core.jar

Android scripting support is not optional if you want android scripting support. When this archive is in the class path of the host application, nano-starbox-core.jar will setup the environment for correct use with Mozilla Rhino JIT. The minimum size requirement for an android release is 2.2 MB.

Rhino Console and Rhino Console Debug are optional desktop features.

Voyager is an optional desktop feature.

This specification does not necessarily detail the API, only the project structure, with a working theory.

Changes to NSR4: JSON Support was moved to package: org.json and now lives in nano-starbox-json.jar

SPEC: NSR4

XML and JNA Support are optional add-ons for all configurations and platforms.

Android scripting support is not optional if you want android scripting support.

Rhino Console and Rhino Console Debug are optional desktop features.

Voyager is an optional desktop feature.

This specification does not necessarily detail the API, only the project structure, with a working theory.

SPEC: NSR3A

Each jar file must have its corresponding dependencies located in the Java Classpath.

Core depends on JRE 1.8 API Level 8
Rhino depends on Core
Web Server depends on Rhino
Rhino Console depends on Rhino and Java Swing
Rhino Debugger depends on Rhino Console
Voyager depends on Core and Java JFX

Rhino Android Support is needed if you want to run NanoStarbox Rhino on an Android device.

Box Full 'O Jars and Zippers

If you want rhino scripts with templates and dynamic server pages, then you'll need the rhino jar, and RhinoWebDriver jar.