ichthyo/LUMIERA.clone
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

DOC: Session Storage, very general introduction.

Browse source
This commit is contained in:
Benny 2012-12-30 23:09:19 +01:00 committed by Ichthyostega
parent 9a894e3719
commit 8a09414e46
1 changed files with 24 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
doc/user/intro/intro.txt
View file

@ -354,10 +354,30 @@ Most of the material in this section is to be found in the proc layer and in the
backend.
Session storage
~~~~~~~~~~~~~~~
[red]#to be written#
Session Storage
~~~~~~~~~~~~~~~
[red]#Deatils to be written#
The current representation of a project resident in memory is internally known
as a session, whereas from a GUI user perspective, this is known as a project.
In this section, we will use the term ``session'' as we discussing the internals
of Lumiera here.
Everything is stored in a session. If a user saves a session, then there should
be no difference to the user whether they continue working or throw all their
work away and load the session that has just been saved. In other words
``everything is stored in a session!''
This ambitious goal has a number of advantages. If all steps are to be stored,
then all steps must be available as an object to be stored. We can perform
operations on these objects. For example unlimited ability to undo previous
steps, selective undo of previous steps or the possibility of merging various
steps might even be a possibility. For example, work on a project at the
office and work on the same project at home can be merged each morning and
evening.
Session storage is envisaged to be performed as databank with logging, some
search facilities and a number of features associated with databanks.
//databank with logging, no data loss.
@ -375,7 +395,7 @@ Placements
~~~~~~~~~~
Generic mechanism to stitch together media objects. Any placement may contain
a list of conditions how to locate the placed object, examples being
a list of conditions on how to locate the placed object, examples being
time-absolute/relative, relative to another object, or relative to some
specific source media frame.