Demos provided as part of the runtime are a convenient way to experience each module's functionality without the need to do special development or connect actual devices. The demos of all modules are placed in the demo/<demo_dir> directory. Each demo should come with a detailed description and instructions, located in a readme.txt file.
Starting a Demo
Using framework console commands
One way to start a demo is directly from the framework text console using system commands:
fw>exec ../../demo/<demo_dir>/install.txt
fw>install -s ../../demo/<demo_bundle.jar>
Using Kit Manager
To use the Kitman Manager, first you need to have the com.prosyst.mbs.util.kitman bundle installed. Then, type 'list' (or just 'ls') in the 'kitman' command group to see all available installation scripts with their corresponding demo script IDs and names. Run the script in one of the following ways:
kitman>install <kit_ID>
kitman>install "<kit_name>"
When starting a demo, it is recommended that you uninstall any previously used demos unless explicitly specified otherwise in the documentation. Use the 'uninstall' command.
Using a demo from Eclipse
The demo project will appear in the Package Explorer of the workbench.
As a pre-requisite for connecting to the OSGi Framework from Eclipse you have to activate the Tooling Client (IAgent).
The demo bundle will appear in the runtime within the Frameworks view.
All dependencies should be resolved manually. Installing a Demo via Eclipse does not install dependent bundles.
Rebuilding a Demo
If you are using Eclipse, a demo is automatically rebuilt when (re)installed/updated on the runtime from the IDE.