3 Commits

Include renames

Author	SHA1	Message	Date
tfaour	fcf3aec4c0	Move button actions to per-widget config, add hold-for-global-action ... Next/back button assignment moves from a frame-level "Button assignments" card into each widget's own gear-icon dialog, prefilled with a sane default at creation (photos/calendar -> advance/back, whiteboard/weather -> check_now, others -> none). At most one binding per (widget, button) now -- cross-widget execution order never mattered since each widget's action only touches its own state. New firmware capability: holding NEXT or BACK past a configurable duration (min 3s, server-side default) triggers a frame-wide action instead of the per-widget short-press one -- cycling saved layouts, refreshing all widgets, or freezing/unfreezing every photo widget (see app/global_actions.py). Firmware next/back checks gain the same hold-duration polling the combo button already had; the threshold comes from the previous wake's /frame/config fetch (persisted in NVS), since this wake's button decision happens before that request. Not done here: firmware/version.txt is intentionally left unbumped -- this hasn't been built or hardware-tested (no ESP-IDF toolchain in this environment), so no firmware release build should be triggered yet.	2026-07-27 22:09:33 +00:00
Thomas Faour	9f3f4b6f62	Add a "Clear all" button to the Layout tab's widget canvas ... One request (DELETE /api/frames/{id}/widgets) removes every widget on the frame in a single locked transaction, cascading their configs and button-action bindings the same way single-widget delete already does. Gated behind confirm() like the existing per-widget remove button, and disabled when there's nothing to clear. Covered by the same owner/ unrelated-user/linked-but-not-controlling permission shape used elsewhere (test_widget_placement.py). Also fixes a real, pre-existing mobile bug this surfaced: the Layout page's .layout grid used a bare `1fr` track on the <860px breakpoint instead of `minmax(0, 1fr)` like the desktop rule already does, so a wide enough descendant (previously nothing hit this; the new title-row button did) would force the whole page into horizontal scroll on phone widths. Verified before/after with the run-server driver's new `viewport` command.	2026-07-25 01:32:25 +00:00
tfaour	5d4bb53b8a	Widget system Phase 4a: widget CRUD + grid placement UI ... Adds the actual "Android home screen" placement experience: a new Layout tab with a pointer-driven canvas for dragging/resizing widgets and adding new ones from a type picker. Backed by a new routers/api_widgets.py (create/move/delete), which re-validates bounds, minimum footprint, and no-overlap server-side regardless of what the client already checked. A widget added without an explicit position lands in the first open space that fits it (grid.find_open_rect), so users don't have to hunt for empty space themselves. Also fixes a real latent bug this surfaced: changing a frame's orientation swaps the widget grid's long/short axis, which left existing widget placements out of bounds on the new grid with no render-time safeguard. Orientation changes now reset the layout to a single full-panel widget (keeping the first widget's type, dropping the rest), with a client-side confirm before it happens.	2026-07-24 12:48:56 -04:00