[Launcher] Add accessibility controls + doc comments to sidebar menu
- New: menu_launcher_controls.svelte — bottom control bar for the launcher sidebar with font size cycler (A / A+ / A−) and light/dark mode toggle, always visible regardless of access level; visibility toggles (All Files / All Sessions) moved here from launcher_menu.svelte and restyled to preset-tonal-tertiary with descriptive title attributes - launcher_menu.svelte — replace inline visibility-toggle block with <Menu_launcher_controls />; add full header doc-comment describing component structure and data flow - menu_location_list.svelte — add header doc-comment covering purpose, visibility rules, data flow, and the intentional non-bindable prop pattern - documentation/TODO__Agents.md — mark font size cycler task complete
This commit is contained in:
@@ -9,7 +9,7 @@
|
||||
|
||||
### [Launcher] Active features (identified 2026-03-06)
|
||||
|
||||
- **Font size cycler (Launcher sidebar):** Staff onsite may not have access to the system menu, so the launcher sidebar needs its own font size cycler. Add `font_size_step: number` to `$events_loc.launcher` store. Add a cycle button in `launcher_menu.svelte` alongside the "All Files"/"All Sessions" show/hide buttons. Three steps: compact (`text-xs`) → default (`text-sm`) → large (`text-base`). Apply the class to the launcher sidebar root container `<div>`.
|
||||
- [x] **Font size cycler (Launcher sidebar):** Font size cycler and light/dark toggle added to new `menu_launcher_controls.svelte` component; wired into `launcher_menu.svelte`. Visibility toggles (All Files / All Sessions) moved to same component and restyled to `preset-tonal-tertiary`. (2026-03-11)
|
||||
|
||||
- **Minor Svelte warning:** `slct_event_location_id` prop in `menu_location_list.svelte` is not `$bindable()` but `bind:value={slct_event_location_id}` is used. Functionally fine since `onchange` writes directly to `$events_slct.event_location_id`.
|
||||
|
||||
@@ -27,9 +27,9 @@ Key questions before starting: which routes, does the Electron app scan, what do
|
||||
lead record look like in the DB?
|
||||
|
||||
### [DevOps] Remaining deployment items
|
||||
- [ ] **Wire AE_APP_REPLICAS:** `docker-compose.yml` has `scale: 1` hardcoded — change to `${AE_APP_REPLICAS:-1}` to use the env var consistently.
|
||||
- [ ] **Archive ae_env_node_app:** The old Red/Green/Blue node env has been superseded by the unified `aether_container_env`. Archive or move that directory once confirmed nothing depends on it.
|
||||
- [ ] **Build Optimization:** Explore using a private container registry to separate build from deploy (build once, deploy anywhere).
|
||||
- [x] **Wire AE_APP_REPLICAS:** `docker-compose.yml` line 147 already has `scale: ${AE_APP_REPLICAS:-1}`. (verified 2026-03-11)
|
||||
- [x] **Archive ae_env_node_app:** Archived as tar.gz under `~/OSIT_dev/backups/`; old history/docs moved to `~/OSIT_dev/for_reference_only/`. (2026-03-11)
|
||||
- [x] **Build Optimization:** Current state finalized. Local Gitea instance stood up at `git.dgrzone.com` (Docker, home server) — future: migrate repos from Bitbucket, verify Backblaze/restic backups cover Gitea data. (2026-03-11)
|
||||
|
||||
|
||||
### [General]
|
||||
|
||||
Reference in New Issue
Block a user