FR-DEV-15 — More than one edit variant per photograph #11
Notifications
Due Date
No due date set.
Blocks
Reference: dtourolle/DarkRoom#11
Reference in New Issue
Block a user
A photograph shall be able to carry more than one edit variant, created and switched from the develop view.
Why
The mono version, the tighter crop, the client's alternative — held at once rather than chosen between. Branching is what makes an irreversible-feeling decision reversible, and it is the answer to "this crop for print, that one for the web" that does not involve editing the frame twice.
The data model already anticipates this.
VersionIdincore/dr-types/src/lib.rs:41is documented as "one edit variant of an image (a virtual copy)";dr-catalog's schema andkeywords.rsboth already reason about virtual copies. Nothing in develop creates one.Acceptance
keywords.rsalready states and tests.Cost
The largest item in the Develop Ergonomics spec, and the only one that is a subsystem rather than a develop feature — it reaches the catalog, the grid, the sidecar and export. Worth staging behind the cheaper comparison work (hold-to-compare, snapshots), which covers a good part of the same need for much less.
Part of the Develop Ergonomics spec (FR-DEV series proposal), 2026-09-05.
Stage behind #3 and #8. Held comparison and named snapshots cover a good part of the same need for a fraction of the cost; do them first and re-judge whether this is still wanted at this size.
Now also needed by #67 (consolidating duplicate originals): when copies of one RAW carry different edits, those edits become virtual copies on the file that survives, so this is what lets #67 merge a group without losing processing.