Building the Package
1
Create a folder with your app name
Let’s use ‘Hello World’ as an example
2
Add a config.conf
The
config.conf should be in the main app folder, do not nest. Add a package name property. The package name cannot contain numbers or whitespace.3
Add Standards
You may add standards to your Standard Package. If you do, create a folder
standardsin the primary app folder and add individual .stds files for each standard or use the installed system standards.4
Add Code
Add any
.std files or other folders containing .std files as the code of your package.5
Pack and Import
To pack your app, zip the app folder and rename to change the extension to The system unpacks the bundle, reads the package name from
.spk instead of .zip. Then, in the Standard System CLI run the pack command.config.conf, and installs it under the local package store at .store/spks/. If the package name already exists, Standard prompts before overwriting it.6
Run
Run the package by package name.You can also run it by the installed folder identifier if you know the folder name under
.store/spks/.Start Key
Packages are read, checked, and ran in alphabetical order for file name. To indicate where you’d like your app to start, use a^. In the example below, the main.std will be ran first as it contains the start key, even though auto.std comes before main.std.
main.std
auto.std
helper.std
start.std