octomy::standalone
The host glue that runs an app with no node: harness, window, context and its facilities.
| Group | standalone |
Detailed description
A standalone app runs the same activities as a node app, but no Node exists. The classes here take the node's place: a harness that starts the app, a window that composes window-features, an activity context that is a pure facility registry, and the confirm, toast, batch and OPAL facilities the app registers in it.
Classes
| Class | What it is |
|---|---|
| StandaloneActivityContext | **Light provider** of octomy::activity::ActivityContext for standalone apps (§SAL-1, §AC-2) |
| StandaloneBatchController | Standalone batch host glue: the "jobs view" over an app's queue (§SAA-1.3, P3) |
| StandaloneCompatBar | Toolbar "compat" strip re-hosting the node-app header controls in a standalone app (§SAL-2.1, P1) |
| StandaloneConfirmController | Standalone confirm host — renders a §NS-5 confirm through the window-level confirm overlay (§SAL-2.4) |
| StandaloneHarness | Shared bootstrap for a standalone (non-node-hosted) GUI app (§SAL-1, §SAA-1.6) |
| StandaloneOpalContext | Light backing of the opalContext facility (§SAL-2.2, D8): the node-free OPAL/LLM stack, stood up once per app |
| StandaloneOpalController | Gives a standalone window the OPAL chat — the Light backing for the OpalChatHost feature that NodeWindow composes too (§SAL-2.2, P2, §ACW-2 slice 5) |
| StandaloneWindow | A window that composes window-features instead of inheriting them (§ACW-3, §ACO W7) |