4 Commits

Include renames

Author	SHA1	Message	Date
stroblmeandClaude Opus 5	518231aa39	Touch is a panel setting, and the rail grows with it ... It described the wrong object. A dashboard is a document that may hang on a hallway tablet and in a desk browser at the same time, and only one of those has fingers on it — so the flag moves off `DashboardDef.settings` and onto `PanelDef` as a plain bool, ticked in the Panels dialog. `useCanvasRoot` takes it as an argument rather than reading the document, and `/panel/{id}` is the only surface with a panel to ask. Dropping the message binding with it is deliberate: nothing drove it, and a flow deciding whether a screen has fingers on it was never the point. A stored `settings.touch` is inert rather than migrated, which `_check_settings` skipping unknown names already guaranteed. The rail was the other half. It had no touch behaviour at all and its 40px buttons met neither branch of the 44/32 rule. `[data-touch] .dui-rail{-item}` in `ui/core/core.css` spends the padding and the gap on the buttons instead, so they reach the 44px target and the rail comes out taller at exactly the same width — `RAIL_INSET` never moves, and the arrangement under it does not either. Also closes the panels-dialog icon gap: `DashboardSummary` carries the `icon` now, so the dialog draws each assigned dashboard's rail glyph beside its checkbox. `initials()` went from three identical copies in the looks to one in `Dashboard/icons.ts`, so the dialog and the rail fall back the same way. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Va7ExQDtuwKN7kNpHhWWNQ	2026-08-31 19:04:20 +02:00
stroblmeandClaude Opus 5	0c17f1fea9	Draw something for an icon or colour name nothing maps to ... An unknown name indexed the map, got undefined and drew nothing — the same as no icon at all, so a typo was invisible. It resolves to a placeholder glyph and the default tint now, and warns once per bad name: both lookups sit in a render, so a bound widget would otherwise warn per value. An empty name still draws nothing, which is what "no icon" means. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KYM38KSb4V4v2T71eifnZv	2026-08-30 16:29:46 +02:00
stroblme	67c35093e6	Add a player widget, and let a slider be drawn as a fader ... The player is the one tile that both reads and publishes, so it has two bindings: it shows a `record` describing what is playing — title, artist, album, status, and position and duration in seconds — and publishes transport words back to one `str` message (`toggle`, `next`, `prev`, `seek:<seconds>`). Those are a streamer's own vocabulary rather than this app's, which is what lets one tile drive whatever is on the other end. The position counts forward in the browser between readings, so the bar moves at one second while the device behind it is polled at whatever rate suits it; every reading that arrives is taken as the truth and the count restarts there. That is also why this is one record rather than five messages — a tile drawn from five would redraw itself five times, and show a new title against the old duration in between. Being both is why `INPUT_WIDGETS` does not gain it: what that set means is "the message this widget publishes is its only binding", which is exactly what a player is not. Its reading is checked the usual way and its `target` separately. The fader beside it needed nothing new. `ui/core` has had `orientation` on the slider all along and all three looks draw it; only the widget never passed it, so a volume control — the one thing reached for without looking, where up is louder — could not be a column. Now it can, and the tile's height is the track.	2026-08-30 14:17:16 +02:00
stroblmeandClaude Opus 5	dbaa3518b9	Bump dashboards: bar, icon, forecast and clock widget types ... Plumbing only: the widget-type literal and its dtype table on both sides, the regenerated client, a curated lucide map and four stubs the renderers are wired to. Also a latching switch and a segmented dropdown, both a `style` on the control that already publishes and reads back, plus the option editor a dropdown never had. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HTsT1isxUjw5gtkJk8WhuA	2026-08-20 08:31:36 +02:00