Support multiple project screens with an active-screen dropdown #5

Open
opened 2026-11-16 13:57:09 +01:00 by Dandaedre · 0 comments
Owner

Allow a project to contain several screen layouts and select the active screen from a dropdown. Display and edit one screen at a time, preserving each layout when switching. This is a distant-future goal with no committed release date; simultaneous multi-screen editing is outside its scope.

Scope and decisions

  • Define screen identity, naming, creation/removal and active-screen selection with a small, clear UI.
  • Define which state belongs to each screen and which is shared: output dimensions, layers, source relationships, references, workspace state and device mappings.
  • Preserve each screen's layout and settings when switching without implicit device actions.
  • Define how import/export, recovery, undo and device transfer scopes relate to the active screen; make the selected scope visible.
  • Document project persistence and version migration before implementation. Existing single-screen projects must keep their layout and behavior.

Acceptance criteria

  • Create at least two distinct screen layouts, switch between them and recover their independent geometry/settings unchanged.
  • Save/reopen and recover a multi-screen project without losing screen identity or content.
  • Migrate existing single-screen projects through tested fixtures, with clear errors for unsupported versions.
  • Verify that import/export and explicit device operations affect only the documented scope, with no automatic send or source-routing changes on screen selection.
  • Update the manual, persistence contracts and meaningful regression tests.

Reference: project stretch goals.

Allow a project to contain several screen layouts and select the active screen from a dropdown. Display and edit **one screen at a time**, preserving each layout when switching. This is a distant-future goal with no committed release date; simultaneous multi-screen editing is outside its scope. ## Scope and decisions - [ ] Define screen identity, naming, creation/removal and active-screen selection with a small, clear UI. - [ ] Define which state belongs to each screen and which is shared: output dimensions, layers, source relationships, references, workspace state and device mappings. - [ ] Preserve each screen's layout and settings when switching without implicit device actions. - [ ] Define how import/export, recovery, undo and device transfer scopes relate to the active screen; make the selected scope visible. - [ ] Document project persistence and version migration before implementation. Existing single-screen projects must keep their layout and behavior. ## Acceptance criteria - [ ] Create at least two distinct screen layouts, switch between them and recover their independent geometry/settings unchanged. - [ ] Save/reopen and recover a multi-screen project without losing screen identity or content. - [ ] Migrate existing single-screen projects through tested fixtures, with clear errors for unsupported versions. - [ ] Verify that import/export and explicit device operations affect only the documented scope, with no automatic send or source-routing changes on screen selection. - [ ] Update the manual, persistence contracts and meaningful regression tests. Reference: [project stretch goals](https://proxy.dandaedre.com/gitea/idle-org/canvas-pilot/src/branch/main/docs/canvas-pilot/plan.md#stretch-goals-distant-future).
Dandaedre added the
enhancement
label 2026-11-16 14:02:46 +01:00
Dandaedre self-assigned this 2026-11-16 14:02:55 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: idle-org/canvas-pilot#5
No description provided.