Plan GUI controls for directional device mappings

This commit is contained in:
Dandaedre 2026-11-18 13:11:53 +01:00
parent 3f299b1d5f
commit e0e9c8d969
4 changed files with 25 additions and 3 deletions

2
Cargo.lock generated
View File

@ -602,7 +602,7 @@ dependencies = [
[[package]]
name = "canvas-pilot"
version = "0.9.49"
version = "0.9.50"
dependencies = [
"base64 0.22.1",
"craft-dwg",

View File

@ -4,7 +4,7 @@ default-members = ["crates/canvas-pilot"]
resolver = "3"
[workspace.package]
version = "0.9.49"
version = "0.9.50"
edition = "2024"
license = "MIT"
repository = "https://proxy.dandaedre.com/gitea/idle-org/canvas-pilot"

View File

@ -4,6 +4,12 @@
## Unreleased
### v0.9.50
- Added a stretch goal for independent load/send mapping controls, multiple send
destinations and eventual named connections, retaining the synchronized workflow
as the default. Implementation remains deferred.
### v0.9.49
- Split load sources from send destination collections internally, keeping existing

View File

@ -106,7 +106,7 @@ checks and stretch goals below remain open; the tag does not mark them complete.
Issue tracking: the adapter goal is already tracked in
[Gitea #1](https://proxy.dandaedre.com/gitea/idle-org/canvas-pilot/issues/1).
The other four have [ready-to-publish issue drafts](../development/stretch-goal-issues.md).
Earlier goals have [ready-to-publish issue drafts](../development/stretch-goal-issues.md).
Publication is pending an issue-enabled token; the current token lacks
`read:issue` and `write:issue`. Preparing an issue does not complete its goal.
@ -147,6 +147,22 @@ Publication is pending an issue-enabled token; the current token lacks
non-AW candidates; the list is a research backlog, not a commitment to support
every product.
- [ ] **Independent load/send mapping controls and multiple send destinations.**
Expose the existing [directional mapping model](../interfaces/canvas-pilot.md#directional-device-mapping-version-19)
in the GUI, keeping the current synchronized, single-destination workflow as
the simple default. Allow an explicit choice to separate the load source from
send targets, then add/remove destinations by screen and layer. Later extend
this to named connections and multiple machines; only the current connection
exists today. Keep this distinct from multiple editor screens below.
Prototype a compact interface before adding functional controls. Make transfer
scope and destination summaries clear, detect overlapping destinations, and
define reconnect, unavailable-target and partial-failure handling before enabling
multi-machine sends. Mapping edits must not trigger device writes. Verify
synchronized/separate edits, undo/redo, save/reopen, recovery and embedded-export
round trips, plus per-destination preflight and readback. The internal split and
fan-out planning shipped in v0.9.49; GUI controls and named connections remain
future work with no committed release date.
- [ ] **Multiple editor screens in one project.** Use a dropdown to select the
active screen, displaying and editing one screen at a time. Preserve each
screen's layout when switching; simultaneous multi-screen editing is outside