[Gzz-commits] manuscripts/FutureVision oplan.txt

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/13 10:33:34

Modified files:
        FutureVision   : oplan.txt 

Log message:
        libvob

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/FutureVision/oplan.txt.diff?tr1=1.14&tr2=1.15&r1=text&r2=text

Patches:
Index: manuscripts/FutureVision/oplan.txt
diff -u manuscripts/FutureVision/oplan.txt:1.14 
manuscripts/FutureVision/oplan.txt:1.15
--- manuscripts/FutureVision/oplan.txt:1.14     Thu Nov 13 10:30:25 2003
+++ manuscripts/FutureVision/oplan.txt  Thu Nov 13 10:33:33 2003
@@ -181,8 +181,6 @@
 that can *show* the versioning, and allow the user
 to merge different users' changes to a document.
 
-Connection types, showing only some (re overload)
-
 3.1 Zzstructure (used in ZigZag(tm))
 ------------------------------------
 
@@ -315,7 +313,53 @@
 ----------
 
 [28] Rewrite to just state problem and solution
-from a high-level POV (Benja).
+from a high-level POV (Benja):
+
+    We have suggested that users should be able to add
+    connections to views programmed by somebody else.
+    For example, when showing meetings on a timeline,
+    it should be easy to add buoys showing the participants
+    of each meeting. To allow such connections to be added
+    without changing the view's code, we have developed
+    Libvob, a flexible user-interface toolkit.
+
+    Libvob provides functionality to not only construct
+    a scene graph (i.e., specify what to draw on the screen)
+    but to also specify which parts of the scene graph
+    correspond to which objects in the application model,
+    the RDF graph in the case of Fenfire. 
+
+    The timeline view, for example, would specify which
+    parts of the scene graph represent each event drawn
+    (events being nodes in the RDF graph). A different view,
+    programmed independently, can iterate through these nodes
+    and connect buoys to each of them. Through the association
+    with part of the scene graph, it knows *where* to connect
+    the buoys to.
+
+    Libvob also uses a directed acyclic graph as the scene graph,
+    rather than the conventional tree; i.e., its graphical model
+    is not hierarchical like that of other toolkits. This provides
+    natural support for transpointing windows (Nelson 1995),
+    i.e., connections between different parts of the view hierarchy:
+    Showing a connection between two different windows is just
+    as simple as showing a box inside a single window, the only
+    difference being that the connection has *two* parents
+    in the scene graph instead of only one.
+
+    This is necessary for the implementation of buoys, which
+    are an instance of transpointing windows (a connection
+    is drawn between the buoy and the part of the main view
+    it is related to).
+
+
+REFERENCES:
+
+    T. Nelson, "The heart of connection: hypermedia unified 
+    by transclusion", Communications of the ACM 38:8, (August 1995)    
+
+    ALSO REFER TO THIS IN RELATED WORK
+
 
 4.4 FenPDF
 ----------