Demos
Applications built from the primitives and the table, the way an application would build them, with a runtime panel under each that reads the page it is on.
On this page
A demo is a screen that looks like software rather than a specimen: several primitives composed on one page, real forms, a table with data, dialogs with consequences. Each one states which parts work with JavaScript disabled and where that is tested; the runtime panel shows the listeners and modules the page costs.
Applications
| Demo | Uses | Status |
|---|---|---|
| Settings application | Tabs, Dialog, Popover, Menu, Switch, Checkbox, Radio group, native select, forms, DataTable | Built. An account-settings screen with a live runtime panel and a without-JavaScript checklist. |
| Command workspace | Command palette, Combobox, Menu, Dialog, keyboard interaction | Not built: the command palette primitive does not exist yet; the combobox does. |
| Data dashboard | DataTable with sorting, filtering and selection, Popover, Dialog, Menu | Not built. The table features and primitives it needs exist. |
| Large dataset explorer | Table, virtual rows, Data Grid mode, editing, keyboard navigation | Not built: there is no virtual module (ADR 0006 extracts one only when the table proves the need). |
What a demo carries
Under the application: the live runtime inspector of the proof page (primitives by tier, shared listeners counted two ways, controllers), the registration modules the build injected for the demo's own files, and a checklist of what works with JavaScript disabled. A checklist entry is called tested only when a spec runs the same markup without script; the rest is marked as expected from the platform and not tested on that page.