Add standalone mapping window visual study
This commit is contained in:
parent
e0e9c8d969
commit
e0da8f6ea1
|
|
@ -602,7 +602,7 @@ dependencies = [
|
|||
|
||||
[[package]]
|
||||
name = "canvas-pilot"
|
||||
version = "0.9.50"
|
||||
version = "0.9.51"
|
||||
dependencies = [
|
||||
"base64 0.22.1",
|
||||
"craft-dwg",
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ default-members = ["crates/canvas-pilot"]
|
|||
resolver = "3"
|
||||
|
||||
[workspace.package]
|
||||
version = "0.9.50"
|
||||
version = "0.9.51"
|
||||
edition = "2024"
|
||||
license = "MIT"
|
||||
repository = "https://proxy.dandaedre.com/gitea/idle-org/canvas-pilot"
|
||||
|
|
|
|||
|
|
@ -4,6 +4,12 @@
|
|||
|
||||
## Unreleased
|
||||
|
||||
### v0.9.51
|
||||
|
||||
- Added a standalone mapping-window visual study with one load source, grouped
|
||||
send destinations and a proposed “Follow load source” shortcut. Sample controls
|
||||
have no application or device logic; production UI and behavior are unchanged.
|
||||
|
||||
### v0.9.50
|
||||
|
||||
- Added a stretch goal for independent load/send mapping controls, multiple send
|
||||
|
|
|
|||
|
|
@ -154,7 +154,8 @@ Publication is pending an issue-enabled token; the current token lacks
|
|||
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
|
||||
Review the [standalone mapping-window mockup](../development/design/mapping-window.md)
|
||||
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
|
||||
|
|
|
|||
|
|
@ -12,6 +12,7 @@ The Python device probe lives in `tools/`; Python tests and build helpers live i
|
|||
| Edit or publish the book | [Manual generation](../manuals/building.md) |
|
||||
| Tasks, acceptance tests and stretch goals | [Project plan](../canvas-pilot/plan.md) |
|
||||
| Stretch-goal Gitea issues | [Existing issue and publication-ready drafts](stretch-goal-issues.md) |
|
||||
| Mapping window visual study | [Mockup and design questions](design/mapping-window.md) |
|
||||
| Multiple project screens | [Design, prototype and testing task](multiple-project-screens.task.md) |
|
||||
| Localization: book, then application | [Task list and acceptance criteria](localization.md) |
|
||||
| Future adapter candidates | [Research and requirements](../canvas-pilot/presentation-switcher-adapters.md) |
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -0,0 +1,65 @@
|
|||
# Mapping window — visual study 01
|
||||
|
||||
[Open the standalone mockup](mapping-window.html) · [Development](../README.md)
|
||||
|
||||
Status: proposal for visual review, not an implemented application window.
|
||||
Open the HTML file locally in a browser. It contains sample data, inline CSS and
|
||||
native controls only: no JavaScript, external assets, storage, network requests
|
||||
or device commands. Dropdown choices do not update other fields or counts.
|
||||
|
||||
## The idea
|
||||
|
||||
Choose an **editor layer** on the left. Read its routes from top to bottom:
|
||||
**one device source → this editor layer → several device destinations**.
|
||||
The source means the device layer from which geometry/appearance is loaded, not
|
||||
its video input or signal routing. The actual Load and Send controls stay outside
|
||||
this mapping editor; Apply mapping would only save routing choices.
|
||||
|
||||
The first connection is the proposed initial connection for a new load mapping;
|
||||
that does not imply automatically choosing a device layer or performing a load.
|
||||
A load source has three explicit parts: connection, device screen and device layer.
|
||||
It can be absent independently of the send targets.
|
||||
|
||||
Send targets are grouped by connection, with screen/layer rows underneath. Repeat
|
||||
an editor layer across different layers on one screen or across screens without
|
||||
repeating the editor controls. Multiple connections are shown only as a collapsed
|
||||
future example; their implementation is not part of this study.
|
||||
|
||||
The useful shortcut is **Follow load source** on the first send target. This is a
|
||||
proposal, not a new saved setting: it would preserve today's simple synchronized
|
||||
workflow while allowing extra independent destinations. Unlinking it would keep
|
||||
its last destination, then allow editing it separately. Whether this should be a
|
||||
persistent relationship or an explicit “Copy load source” action needs agreement
|
||||
before changing the schema. Removing a load source must never silently delete or
|
||||
retarget send destinations.
|
||||
|
||||
The list shows small source/target counts so a layer with no routes or several
|
||||
destinations is easy to spot. It deliberately avoids a large checkbox matrix:
|
||||
connection × screen × layer combinations would quickly overwhelm that layout.
|
||||
|
||||
## Questions for visual review
|
||||
|
||||
- Is the selected-layer approach comfortable, or is a project-wide route overview
|
||||
also needed? Start with this focused editor; an overview can remain a separate view.
|
||||
- Does “Follow load source” communicate the link clearly? A linked row should be
|
||||
read-only in the real UI until unlinked; native controls here are illustrative.
|
||||
- Should adding a destination open a searchable connection/screen/layer picker,
|
||||
then place the result in its connection group? This avoids three permanent
|
||||
selectors for connections that are already grouped.
|
||||
- Should mapping edits use Apply/Cancel as shown, or immediate undoable changes?
|
||||
Apply/Cancel is a proposal for review, not a change to current behavior.
|
||||
|
||||
## States to design next, before implementation
|
||||
|
||||
Unmapped/send-only/load-only layers; unavailable connections; conflicting send
|
||||
destinations; different screen resolutions; large layer lists; narrow windows;
|
||||
keyboard navigation and long translations. A future connection selector needs
|
||||
explicit identities and reconnection behavior, not automatic matching by name.
|
||||
|
||||
A resolution mismatch should remain an actionable validation result until an
|
||||
explicit sizing policy is agreed. Do not invent automatic scaling in this window.
|
||||
Multi-device execution and partial failures belong to a later transfer review.
|
||||
|
||||
The existing [stretch goal](../../canvas-pilot/plan.md#stretch-goals-distant-future)
|
||||
and [mapping contract](../../interfaces/canvas-pilot.md#directional-device-mapping-version-19)
|
||||
remain authoritative for implemented scope. This mockup changes neither.
|
||||
Loading…
Reference in New Issue