<node TEXT="2D space where you can place all data which is dedicated to one project for exchange between apps and for organizing them. 
Things like files, notes, link to disks, link to all the apps you need, .. And also there should be a clipboard where files can be stored temporarily for exchange between different apps.
Depending on what file the user is clicking it leads directly to one of the 'Stages' within Lumiera." ID="ID_903148200" CREATED="1421690272218" MODIFIED="1428008690848" COLOR="#333333" BACKGROUND_COLOR="#f0f0f0">
which <font color="#ff0000">stage</font> is open, which <font color="#ff0000">deck</font> active and which <font color="#ff0000">layer</font>  is on. you can also adjust this per mouse click.
users have their own <font color="#ff0000">settings</font>, they can overrule <font color="#ff0000">system set-up</font>'s and vice versa. it have to be clearly displyed whose <font color="#ff0000">settings</font> are the actual active ones.
</p>
<p>
</p>
<p>
<font color="#ff0000">set-up'</font>s are devided by <font color="#ff0000">locations</font>, the system should automatically add a new <font color="#ff0000">set-up</font> when other displays are connected. you can set it also to not switch and just ignore different hardware
</p>
<p>
</p>
<p>
how audio plays back..
</p>
<p>
the clips and all the media have a <font color="#ff0000">position in 3D space</font>, when it comes to playing here int the <font color="#ff0000">set-up</font> it is choosen how it mixes to the specific hardware
to translate human moves or a serie of moves into '<font color="#ff0000">gestures</font>'. depending an what is active on the '<font color="#ff0000">ground layer</font>' this will performe modification on the '<font color="#ff0000">material</font>'
automatic or manual group <font color="#ff0000">objects</font> with a few different render options for the <font color="#ff0000">groups/bins</font>. bins are universal <font color="#ff0000">objects</font> which can transform to finished <font color="#ff0000">timelines</font> and can be viewed in all the '<font color="#ff0000">Views</font>' provided in the '<font color="#ff0000">Editor</font>' <font color="#ff0000">stage</font>. '<font color="#ff0000">Views</font>' are <font color="#ff0000">sub stages</font>.
</p>
<p>
In '<font color="#ff0000">Project Organizer'</font> you have to define <font color="#ff0000">settings</font> for each <font color="#ff0000">project</font> such as how many <font color="#ff0000">sub-stages</font> you will see, which hardware interfaces, how detailed options you want to see when exporting,... there should be some <font color="#ff0000">pre-configured scenarios</font> five or so which covers all your needs. one of them should be '<font color="#ff0000">easy setup</font>' for beginners, online production,... and pro users can make their own.
</p>
<p>
this <font color="#ff0000">settings</font> can be easily modified during the editing process but the aim is to have as less things around as possible.
</p>
<p>
maybe it's good to select a <font color="#ff0000">user</font> here so that every project can include one ore more <font color="#ff0000">users</font> and they can have their <font color="#ff0000">configurations</font>  (environment).
<node TEXT="same subpoints as A. 'Deck B' is not visible by default to provide a simple first experience for new users." ID="ID_210143166" CREATED="1424543017772" MODIFIED="1424543225828" COLOR="#333333" BACKGROUND_COLOR="#f0f0f0">
<node TEXT="a second deck which is situated left from A. The user can swich between A and B totally or show them in differen proportion. You can use one as in other NLE's to view the source media and the other for a sequence or have two parts of the same sequence open for comparison or easy coping clips around.
there is always one deck/ viewer active so that our navigation input by any interface always adresses one.

Deck B has two different loads, the manual loaded material and a second temporarely show clip board with clip history. at the moment i don't know how and when to switch between this two. there have to be something like a 'clear' button which get rid of the clipboard content." ID="ID_1788168808" CREATED="1421869204062" MODIFIED="1428008682966" COLOR="#333333" BACKGROUND_COLOR="#f0f0f0">
all the<font color="#ff0000"> stages</font> should be available in a mouse/touch and keyboard/'lumiera hardware interface' only version. so that there are different environments without compromises
</p>
<p>
</p>
<p>
every <font color="#ff0000">user</font> should have the possibility to show only his/her most important <font color="#ff0000">stages</font>.
</p>
<p>
</p>
<p>
<font color="#ff0000">stages</font> can have many view options, this are the '<font color="#ff0000">views</font>'. views are pre-configured by the system <font color="#ff0000">set-up</font> or by the <font color="#ff0000">user</font>. for example: show waveform, detailed zoom, ..
</p>
<p>
every view should be as intuitive and clear as possible. this small fragments of the system should really try to do 'one thing at a time'. it should allow an emotional link to what is going on.
</p>
<p>
</p>
<p>
there should be the possibility to <font color="#ff0000">save/mark/create 'subviews'</font>  or '<font color="#ff0000">presentation state</font>' which stores specific position, selections, active commands, active clips, small details.. during one working scession to come by another time. this can be called '<font color="#ff0000">worksite</font>' (idea by hermann).
</p>
<p>
another thing inside <font color="#ff0000">views</font> are '<font color="#ff0000">commands</font>' which are the modifying tools. they are also '<font color="#ff0000">subviews</font>' with some minor graphical changes to the actual <font color="#ff0000">view</font> to show that the <font color="#ff0000">command</font> is on and to let you intuetivly know what to modify. the command is performed by '<font color="#ff0000">gestures</font>' this are a set of human inputs through various devices (<font color="#ff0000">input devices</font>). <font color="#ff0000">gestures</font> define how the <font color="#ff0000">command</font>  is performed.
</p>
<p>
and for some <font color="#ff0000">views</font> in some <font color="#ff0000">substages</font> e.g. in the '<font color="#ff0000">title text tool</font>' there can be the possibility to save <font color="#ff0000">templates</font> as one possible <font color="#ff0000">subview</font>. so that the user can manage to be very efficient when he/she has a repitative task by setting presets and hiding features.
</p>
<p>
</p>
<p>
also note that a change of input device (mouse to keyboard or 'lumiera interface') should happen when you switch between views, and stages only! for continuety in the workflow.
</p>
<p>
</p>
<p>
why the '<font color="#ff0000">screens</font>' and '<font color="#ff0000">stages</font>' together are such a long list: <b>A</b>. to have less buttons and distracting things around when you want to focus on one task. (one thing at a time vs. multitasking and windows) <b>B</b>. because the main input tool should be a wheel which makes it easy to switch around in a linear way (thats what we have to do anyways while editing movies)
magazine (newspaper) view, where you can explore your shooting. with description and tagging clips inside this <font color="#ff0000">bin/sequence/group </font>
</p>
<p>
or have jsut one <font color="#ff0000">clip</font> open
Loose arrangement and clip connecting in 2D space. object based montage.
</p>
<p>
'<font color="#ff0000">Relation Spyder</font>' tool which sets the relations throught a static wall of clips, this produces a fexible line which is/become a new object (sequence) --> define time as a flexible line object
<node TEXT="arrange clips according to the 'time ray' or line, so now the time goes continually forward " ID="ID_1791626974" CREATED="1421833865857" MODIFIED="1424546603557" COLOR="#333333" BACKGROUND_COLOR="#f0f0f0">
<node TEXT="in a track based linear manner (very classical)" ID="ID_1081334440" CREATED="1421834029165" MODIFIED="1424546742689" COLOR="#333333" BACKGROUND_COLOR="#f0f0f0">
<node TEXT="its possible to create relations between objects e.g. Master-Slave for undertitle positions, effects, clip X on a specific point in time is linked to clip Y on a specific point in time, clip Z is linked to a 'track' object on time 0,0 (which is a normal track based timline);
..........." ID="ID_724972898" CREATED="1421877384276" MODIFIED="1424546663727" COLOR="#333333" BACKGROUND_COLOR="#f0f0f0">
This is for time based views only. Each deck have one playhead. Playheads are static in the middle of the viewer and the media is transported through. (so we don't have the situation that the playhead is moving through the window and the timeline have to jump afterwards.)
</p>
<p>
</p>
<p>
curtains
</p>
<p>
each <font color="#ff0000">sub-stage</font> can offer up to three different levels of details. form very simplistic to all  information available. like curtains on a stage and each one opens more depth showing more of the stage.
<font color="#ff0000">configuration</font> as a <font color="#ff0000">layer</font> should show only <font color="#ff0000">options</font>  which are relevant to what we see now, underneath this <font color="#ff0000">layer</font>. so to say every <font color="#ff0000">stage</font>, <font color="#ff0000">view</font>, ... have their own <font color="#ff0000">meta page</font> where all the <font color="#ff0000">options</font> are stored. also if some <font color="#ff0000">options</font> are relative or overruled by more general <font color="#ff0000">configurations</font> or the <font color="#ff0000">system set-up</font>, it is shown here and greyed out
this layer puts detailed information over everything actual on the screen and should act as a quick lookup. there can also be <font color="#ff0000">git-tickets</font>  on the <font color="#ff0000">elements</font> for easy <font color="#ff0000">user-feedback</font>.
to use with <font color="#ff0000">mouse</font>: since we have no buttons in this concept all the available commands (case sensitive) will be shown e.g. on right button click. then there is a graphical representation of each command arround the mouse in circles and sorted by topic. some <font color="#ff0000">modulation keys</font> are available to.
</p>
<p>
it would be great if that could evolve to a standard in all open source creative media applications so that's easy to switch over to a application which you use seldom and start right away. a kind of a fallback or standarized interface. not the functions have to be the same but how they are arranged and how they are accesd and maybe how they are performed (gestures).
<node TEXT="i am planning to make a hardware interface optimized for this concept and somehow usable for other nle's" ID="ID_1912685880" CREATED="1424554265505" MODIFIED="1424554327543" COLOR="#333333" BACKGROUND_COLOR="#f0f0f0">
<node TEXT="pro users can config their own funktion set to do some steps of processing within the OS file browser or in the 'workboards'. e.g. process footage for import, archive footage, archive projects, make online version of an project (this only works if the sequences are available as singular files)" ID="ID_1447355109" CREATED="1424544363160" MODIFIED="1424544537727" COLOR="#333333" BACKGROUND_COLOR="#f0f0f0">
however the relation to the OS looks like, at some point it will be interesting how we can trip arrount between lumiera and other software. so the interaction i think should be very well implemented in the concept.
</p>
<p>
here i suggest '<font color="#ff0000">workboards</font>' which contain project files on a 2d space like a desktop and a clipboard to hand them from one program to anoter. files can also be grouped freely or by software they belong to. there can be some alternative views like in a magazine view. they contain a whole project. you can open them in lumiera (see: stage/project organizer) or as a stand alone full screen app. in case of 'elementaryOS' as a host system there are options like 'D-bus' or 'contractor' which can be used i guess.
