Plan Midra layer management and scoped exports
This commit is contained in:
parent
d752d9b118
commit
0d0a7970c4
|
|
@ -274,6 +274,54 @@ Gate: a reviewed layer-format change can be applied and checked on a designated
|
|||
non-live target. Any use on the current live installation requires separate,
|
||||
explicit authorization at that time. No API calls are part of this planning task.
|
||||
|
||||
### 11. Later stretch goal: layer management and export scope
|
||||
|
||||
Status: requested for later. This is local document organization; it can be
|
||||
implemented independently of step 10 and does not authorize device connectivity.
|
||||
Folders are an optional follow-up, not a prerequisite for adding/hiding layers.
|
||||
|
||||
- [ ] Replace the fixed two-layer document with a collection using stable local
|
||||
IDs. Add an **Add layer** button and editable names. New local layers start
|
||||
visible and unmapped; adding a planning layer does not create a hardware layer.
|
||||
- [ ] Add per-layer **Show / Hide** controls in the layer list. Hidden layers
|
||||
keep their geometry and mapping, remain accessible in the list, and are excluded
|
||||
from canvas drawing and hit testing. Hiding is local only: never send a device
|
||||
hide, clear, opacity or routing command as a side effect.
|
||||
- [ ] Add an **Options → Layer mapping** section that maps each local layer to
|
||||
an explicit device/profile, screen and Midra layer ID. Keep local names and list
|
||||
order independent of hardware identity; reordering or hiding must not remap.
|
||||
- [ ] Add an export-scope choice: **Specific layer…** or **Visible layers only**.
|
||||
The specific-layer picker uses local names and shows the mapped destination;
|
||||
allow intentionally exporting a hidden layer through this explicit selection.
|
||||
Visible means enabled in the layer list, not currently inside the viewport,
|
||||
uncovered by another layer or selected on the canvas.
|
||||
- [ ] Preview the exact included layers, geometry and destination mappings before
|
||||
export. An empty visible set gives an explanation and produces no output.
|
||||
Preserve deterministic list order and never include excluded layers implicitly.
|
||||
- [ ] For device-targeted exports or a future API send, require mappings for every
|
||||
included layer and reject unsupported destinations or duplicate destination
|
||||
mappings within that export. Alternative local layouts may share a destination
|
||||
when only one is included. Generic coordinate copies may remain unmapped.
|
||||
- [ ] Keep export scope distinct from transport: exporting/copying a configuration
|
||||
does not send it. Future device writes still use step 10's separate reviewed,
|
||||
explicit send action, including an explicit Program/Preview target.
|
||||
- [ ] Make layer creation and visibility changes undoable. When session save/load
|
||||
is added, preserve stable IDs, names, geometry, visibility and mappings. Extend
|
||||
selection, paste targeting and undo so they no longer depend on array indices.
|
||||
- [ ] Optional: add named folders with expand/collapse and drag-to-organize.
|
||||
Folders organize local layers; they do not introduce geometry transforms or
|
||||
hardware groups. Collapsing a folder changes only the list display. If folder
|
||||
visibility is added, effective visibility is the layer's own setting AND all
|
||||
ancestor-folder settings; hiding a folder must preserve child visibility choices.
|
||||
- [ ] Test adding layers, hidden-layer selection through the list, stable mappings
|
||||
after reorder, paste/undo targeting, both export scopes, empty scopes, unmapped
|
||||
or conflicting targets, and optional nested-folder visibility. Confirm that
|
||||
organization and export preparation produce no device calls.
|
||||
|
||||
Gate: maintain several local layout alternatives, map them explicitly in Options,
|
||||
then export one named layer or exactly the visible set without changing local
|
||||
geometry, overwriting a conflicting destination silently, or contacting a device.
|
||||
|
||||
## Coordinate contract to verify
|
||||
|
||||
Proposed internal model: screen origin at its top-left, X increases rightward,
|
||||
|
|
|
|||
|
|
@ -99,6 +99,12 @@ Reference artwork is illustrative, not a loaded image or live video. Source/inpu
|
|||
formats, custom output resolution, image import, cropping, alignment and persistent
|
||||
session files are future work. Sessions currently live only in memory.
|
||||
|
||||
[Layer management and export scope](midra-layout-plan.md#11-later-stretch-goal-layer-management-and-export-scope)
|
||||
are also later stretch goals: **Add layer**, local **Show / Hide**, Midra layer
|
||||
mapping in **Options**, and export of a **specific layer** or **visible layers
|
||||
only**. Optional folders would organize local layers. Visibility and organization
|
||||
will not send commands or change the live device.
|
||||
|
||||
Applying layer format through the WebRCS REST API is a
|
||||
[later stretch goal](midra-layout-plan.md#10-later-stretch-goal-apply-layer-format-through-the-webrcs-rest-api).
|
||||
The currently connected Eikos is live: this work must remain offline, with no
|
||||
|
|
|
|||
Loading…
Reference in New Issue