represent the fork
As Lumiera Architect,
I want a generic and recursive representation of the Fork ("track tree") within the UI-Layer,
to accommodate to any arrangement of scopes and content supported by the core model, without limitation by a fixed UI-widget structure.
Change history
(13)
| Keywords: |
GTK added; gtk removed
|
| blockedby: |
1185 → 1185, 1193
|
| blocking: |
1016 → 1016, 1209
|
| blockedby: |
1185, 1193 → 1219, 1193
|
| blocking: |
1016, 1209 → 1016, 1209, 1229
|
| blockedby: |
1219, 1193 → 1193, 1219
|
| Keywords: |
timeline added
|
| blocking: |
1016, 1209, 1229 → 1016, 1209, 1229, 1252
|
| blocking: |
1016, 1209, 1229, 1252 → 1016, 1209, 1229, 1252, 1265
|
| blocking: |
1016, 1209, 1229, 1252, 1265 → 1016, 1209, 1229, 1252, 1265, 1266
|
| blockedby: |
1193, 1219 → 1039, 1193, 1219
|
| blockedby: |
1039, 1193, 1219 → 1039, 1219
|
| blocking: |
1016, 1209, 1229, 1252, 1265, 1266 → 1016, 1193, 1209, 1229, 1252, 1265, 1266
|
| Description: |
modified (diff)
|
| Resolution: |
→ done
|
| Status: |
new → closed
|
| blockedby: |
1039, 1219
|
| blocking: |
1016, 1193, 1209, 1229, 1252, 1265, 1266
|
| Parent Tickets: |
→ 1016, 1193, 1209, 1229, 1252, 1265, 1266
|
| Sub Tickets: |
→ 1039, 1219
|
Over the course of the last years, the UI backbone and top-level context has been thoroughly reworked, to support the kind of highly flexible and dynamic model structure envisioned for Lumiera. Moreover, the custom Timeline widget was dissected and rebuilt from scratch, to accommodate to the new requirements for GTK-3, and to support the aforementioned flexibility. Resulting from this design and architecture work, the new
stage::timeline::TimelinePageencompasses a flexible structure of nested Track-Presenters, which act as UI model of the Fork and are connected to the UI-Bus both to send commands and to be manipulated through »Diff Messages«During this rework, it became clear that besides the regular »Tracks«, the Lumiera UI will also feature »Ruler Tracks« to handle meta informations, like e.g. an overview display, markers and effect ranges, or the notorious time grid display. This turned out to be a rather elaborate additional feature, and will be postponed and addressed later, when the Core Model is more mature. Beyond that, this topic can be considered as settled by now.