diff --git a/doc/devel/draw/UI.Timeline-1.svg b/doc/devel/draw/UI.Timeline-1.svg new file mode 100644 index 000000000..0494c58a5 --- /dev/null +++ b/doc/devel/draw/UI.Timeline-1.svg @@ -0,0 +1,1763 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + Ichthyostega + + + Lumiera: basic organisation of the timeline UI + 2016 + + + + + + + + + + + + + + + + + + + + Timeline + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Clip-1 + + + + + + + + + + + + + + + + + + + + + + + + + + Clip-2 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ...scope ruler... + + ...scope ruler... + + + ...scope ruler... + + + + ...scope ruler... + (collapsed)Track + + Time Ruler + Navigator + Timeline Pane Button Bar + scrollbars + Header Pane + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Clip-3 + + + + Audio + + + + + Video + + + + + + + + + + + + + + + + + + + + + + + + + Effect + + + + + + Marker + + + + Marker + + + + Marker + + diff --git a/wiki/draw/UI-TimelineLayout-1.png b/wiki/draw/UI-TimelineLayout-1.png new file mode 100644 index 000000000..7d4025196 Binary files /dev/null and b/wiki/draw/UI-TimelineLayout-1.png differ diff --git a/wiki/renderengine.html b/wiki/renderengine.html index a834af19c..4b0027241 100644 --- a/wiki/renderengine.html +++ b/wiki/renderengine.html @@ -2797,7 +2797,7 @@ Now, when invoking an operation on some public interface, the code in the lower 
A specially configured LumieraPlugin, which actually contains or loads the complete code of the (GTK)GUI, and additionally is linked dynamically against the application core lib. During the [[UI startup process|GuiStart]], loading of this Plugin is triggered from {{{main()}}}. Actually this causes spawning of the GTK event thread and execution of the GTK main loop.
-
+
Within the Lumieara GUI, the [[Timeline]] structure(s) from the HighLevelModel are arranged and presented according to the following principles and conventions.
 Several timeline views may be present at the same time -- and there is not necessarily a relation between them, since »a Timeline« is the top-level concept within the [[Session]]. Obviously, there can also be several //views// based on the same »Timeline« model element, and in this latter case, these //coupled views// behave according to a linked common state. An entity »Timeline« as represented through the GUI, emerges from the combination of several model elements
 * a root level [[Binding|BindingMO]] acts as framework
@@ -2810,7 +2810,8 @@ Several timeline views may be present at the same time -- and there is not neces
 Session, Binding and Sequence are the mandatory ingredients.
 
 !Basic layout
-The representation is split into a ''Header pane'' exposing structure and configuration, and a ''Content pane'' extending in time. A ''Time ruler'' running alongside the content pane represents the //position in time.// Beyond this temporal dimension, the content area is conceived as a flexible working space. This working space //can// be structured hierarchically -- when interacting with the GUI, hierarchical nesting will be created and collapsed on demand. Contrast this with conventional editing applications which are built upon the rigid notion of "Tracks": Lumiera is based on //Pipes// rather than Tracks.
+[>img[Clip presentation control|draw/UI-TimelineLayout-1.png]]The representation is split into a ''Header pane'' exposing structure and configuration, and a ''Content pane'' extending in time. The ''Time ruler'' running alongside the top of the content pane represents the //position in time.// Beyond this temporal dimension, the content area is conceived as a flexible working space. This working space //can// be structured hierarchically -- when interacting with the GUI, hierarchical nesting will be created and collapsed on demand. Contrast this with conventional editing applications which are built upon the rigid notion of "Tracks": Lumiera is based on //Pipes// rather than Tracks.
+
 In the temporal dimension, there is the usual scrolling and zooming of content, and possibly a selected time range, and after establishing a ViewerPlayConnection, there is an effective playback location featured as a "Playhead"
 The workspace dimension (vertical layout) is more like a ''Fork'', which can be expanded recursively. More specifically, each strip or layer or "track" can be featured in //collapsed// or //expanded state.//
 * the collapsed state features a condensed representation ("the tip of the iceberg"). It exposes just the topmost entity, and might show a rendered (pre)view. Elements might be stacked on top, but any element visible here //is still accessible.//