diff options
| -rw-r--r-- | todo.org | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -21,6 +21,18 @@ The vocabulary is open — topic tags are coined as needed — so these are conv - *Effort / autonomy*: =:quick:= a spare-moment fix (minutes, not a sitting); =:solo:= Claude can carry it end to end — there's a build path, a test path, and no upfront decision needed (a leftover manual spot-check doesn't disqualify it). - *Topic / area* (open): the subsystem a task touches — e.g. =:hyprland:= =:waybar:= =:mpd:= =:music:= =:network:= =:tooling:= =:llm:= =:eask:= =:pocketbook:= =:cmail:=. Coin a new one when it aids filtering. * Archsetup Open Work +** DOING [#B] Widget gallery upgrades :feature:design: +Usability + documentation pass over the [[file:docs/prototypes/panel-widget-gallery.html][panel widget gallery]], orthogonal to the component-generation spec work, so it runs on the =gallery-upgrades= branch (squash merge to main after Craig's UI confirmation + tweaks). Items 1-4 run as a no-approvals speedrun (Craig authorized 2026-07-12); item 5 is a joint brainstorm after the merge. +*** TODO Widget size increase +Render the cards ~3x larger — at the current size visual adjustments are hard and the descriptive text is unreadable. Ship a size toggle (1x/2x/3x, default 3x) so the dense overview stays reachable. +*** TODO Palette display +A section displaying every design token the gallery depends on (swatch + name + value), read live from the generated =:root= block so it can't drift from tokens.json. +*** TODO Alternate screen colors + chip toggles +Identify the period-authentic color families for the screen/glow widgets (phosphor green vs the current amber; nixie neon red; VFD blue-green; P4 blue-white) and answer which greens are shared vs deliberately distinct (phos / vfd / sevgrn / jewel-g are currently four different greens). Add per-card color chips to flip the appropriate widgets between families; apply the first round to the clearly-screen widgets. +*** TODO Per-component info blocks +Every card gets a structured info panel: how to manipulate it (always — currently inconsistent), the UI/UX problem it solves, common vs specialty, where it shines, input model (click-only / drag-only / both — drag has no Emacs equivalent, so click-drivability matters per target) and what click does, limitations, industry/origin, difficulty, when to prefer it over neighbors, and a period marker where the component is clearly not timeless (so period-consistent consoles can swap newer components for historical counterparts). +*** TODO Component classification taxonomy +Brainstorm WITH Craig (after the squash merge, not solo): break the components down by use — freeform output, binary selection, multi-selection, fine-tuning, etc. The taxonomy identifies use-cases with no appropriate component, which fills out the gallery with some confidence of completeness. ** DOING [#B] Retro widget catalogue :feature:design: The panel widget gallery ([[file:docs/prototypes/panel-widget-gallery.html][docs/prototypes/panel-widget-gallery.html]]) grows into a retro-instrument component catalogue: reference photos of period hardware → gallery cards (the visual + behavioral spec) → reusable components for three targets (emacs svg.el, web/React, waybar). Tokens single-sourced in [[file:docs/prototypes/tokens.json][tokens.json]] (gen_tokens.py emits web/waybar/elisp); svg.el proof widget shipped (gallery-widget.el, needle gauge). Reference photos live in [[file:working/retro-stereo-widgets/][working/retro-stereo-widgets/]]. R-series cards (R01-R31) are the reference-derived widgets — collection phase COMPLETE 2026-07-12 (84 cards, all behaviorally verified). |