3 Commits

Include renames

Author	SHA1	Message	Date
tfaour	a33a3a71e4	Widget system Phase 4b: per-widget gear-icon config dialogs ... Replaces the Photos/Calendar/Whiteboard tabs with a single Layout page (now the frame's landing route) where each widget gets a gear icon opening a dialog scoped to that specific widget's own settings. This was the missing piece for genuinely independent same-type widgets -- "the Calendar tab" never made sense once a frame could hold more than one calendar widget with different settings. Data layer: FrameCalendar re-keyed from frame_id to widget_id, so each calendar widget has its own independent included-calendars set. The rekey runs as an unconditional post-startup step (like the existing widget backfill), not a numbered migration -- it depends on calendar widgets already existing, which themselves come from that same backfill step, not from schema migration. Registering it as a numbered migration would have run it first during a real upgrade, silently dropping every row; caught by a new test that exercises the raw-SQL upgrade path instead of the fresh-install create_all() shortcut every other migration test takes. API layer: every endpoint that used to assume "the frame's widget of this type" (photo queue/thumbnail/preview, calendar select/color/ tasks/weather, whiteboard source/browse/preview) moved into api_widgets.py under /api/frames/{id}/widgets/{widget_id}/..., with a new require_widget_view/control dependency pair mirroring the existing frame-level ones. Device status (battery/last-seen/firmware) got its own frame-level /status endpoint, split out of the old photo-specific /queue it used to piggyback on -- fixes the status bar going silently blank on any frame without a photo widget. UI layer: each widget type's existing settings markup/JS was ported into a dialog partial + an explicit init/close function pair (the content is now fetched and injected on demand, not loaded at page load time). window.FRAME_API is repointed to the open dialog's widget-scoped API base for its duration and restored on close; a separate window.FRAME_BASE_API stays stable for the always-present header/ status-bar scripts. Caught during manual browser testing: the consolidated config-save endpoint initially expected a JSON body while the copied-over dialog JS posts form-urlencoded data (the old convention) -- fixed to match, with new HTTP-level test coverage that would have caught it immediately.	2026-07-24 14:31:24 -04:00
tfaour	37bd657299	Widget system Phase 2: full cutover to widget-based rendering ... device.py's mode-keyed dispatch is replaced by a real compositor: load a frame's widgets, compute pixel rects via app/grid.py, render each through its widget module, and composite with render_panel. Physical NEXT/BACK buttons now execute each frame's assigned FrameButtonAction rows instead of one hardcoded per-mode action. api_frames.py, manage.py, and common.py's build_manage_content are repointed to read/write the frame's widget config rows instead of the old Frame columns, and every settings page (Photos/Calendar/ Whiteboard tabs) now pre-fills its form from the same widget config the write endpoints actually save to -- previously the read and write sides would have silently diverged. The old mode selector and photo-inlay checkbox are removed along with their now-inert wiring; arbitrary widget placement subsumes what the fixed inlay split did. Ships together with Phase 1 (per-type render/action modules) since splitting the read/write cutover across deploys would have left settings changes with no visible effect.	2026-07-24 09:26:28 -04:00
tfaour	31adc34a19	Add a real pytest suite, gating the CI build ... 64 tests covering: auth/setup and the CSRF gate, the "owner adds their own data, anyone linked can mute it" permission pattern shared across calendar-select/tasks-source/whiteboard-source, migration correctness (fresh install, idempotent re-run, expected columns), battery estimate outlier rejection, calendar_feed's fetch/merge/partial-failure handling, webdav_client's fetch/list-directory, the whiteboard force-refresh throttle bypass and browse endpoint, and render-size invariants across calendar views/orientations. No DB/HTTP fixtures need Docker, Node, or a real Immich/CalDAV/WebDAV server -- a fresh temp SQLite file plus a couple of small local HTTP servers as test doubles cover it all. Table data is wiped and reseeded between tests rather than relying on SQLAlchemy's transaction-rollback isolation pattern, which needs a pysqlite event-listener workaround app/db.py's engine doesn't have and has no reason to gain just for tests. Wired into .gitea/workflows/server-docker-build.yml as its own job that build-and-push now depends on, so a failing suite blocks the image push rather than just running alongside it for show.	2026-07-23 18:51:54 -04:00