[Gzz-commits] libvob/doc design.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/libvob
Module name:    libvob
Changes by:     Benja Fallenstein <address@hidden>      03/03/16 09:55:26

Modified files:
        doc            : design.rst 

Log message:
        twiddle

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/libvob/libvob/doc/design.rst.diff?tr1=1.1&tr2=1.2&r1=text&r2=text

Patches:
Index: libvob/doc/design.rst
diff -u libvob/doc/design.rst:1.1 libvob/doc/design.rst:1.2
--- libvob/doc/design.rst:1.1   Mon Feb 24 06:33:14 2003
+++ libvob/doc/design.rst       Sun Mar 16 09:55:26 2003
@@ -2,21 +2,30 @@
 Design of LibVob
 ===========================
 
-The fundamental design goal of the LibVob toolkit is to allow
-smooth interpolation between independent views as well as 
-drawing connections between objects cross-cutting the view hierarchy.
+The goal of the LibVob toolkit is to allow
+interpolation between independently programmed views as well as 
+drawing 'cross-cutting' connections between objects 
+in different places of the view hierarchy. 
+(For example, a connection between objects in two
+different windows would be 'cross-cutting' as it
+connects two different places in the hierarchy.)
 
 This distinguishes the Vob system from normal scene graphs:
 instead of one global scene graph, there are *keyframe* scene
 graphs. 
-After each discrete user action, a new scene graph is generated
+After each discrete user action (like a key press or mouse click), 
+a new scene graph is generated
 by the user-specified *view*.
-Then, the previous keyframe is smoothly animated into the
+Then, the previous keyframe is animated into the
 new keyframe to allow the user to keep track of all changes.
 The animation is governed by *keys* associated with the
-visible objects; the keys are taken from the underlying 
-model and enable two independently developed views to still
-smoothly interpolate into each other.
+visible objects; an object in the first scene graph
+is animated to an object in the second scene graph
+if both have the same key. The keys are taken from the same
+underlying model (for example, they could be cells in a
+spreadsheet) and enable two independently developed views
+to be interpolated to each other (for example, two different
+ways to render spreadsheet data in a graph).
 
 Continuous user actions (e.g. zooming/panning with the mouse)
 are treated more conventionally by editing the parameters of