The StackRunner Home stack is designed to be a minimal script only stack that is run once at startup. It should be possible to be run from disk or loaded remotely using go url. It should do everything that is needed to get the project up and running, but nothing more.
In particular it should: - have no dependencies - not depend on script introspection - use robust file naming conventions - human readable and easy to parse in any language - a simple text stack that plays well with revision control The stack should: 1. Load key minimal libraries for menus and shared dependencies (lib_MenuText, lib_MenuPop, and lib_Common) 2. Open the Data|View module (provides StackRunner interface) 3. Provide initital startup greeting. 4. Provide a universal name-space reference that all project rely on.
# Testing
# See - Why LCW Names us a flat naming convention - Home Stack and the stackfiles property - StackRunner - Naming Convention and the Global Namespace