gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] gzz/doc/pegboard/buoydesign--tjl peg.rst


From: Tuomas J. Lukka
Subject: [Gzz-commits] gzz/doc/pegboard/buoydesign--tjl peg.rst
Date: Sat, 01 Feb 2003 12:32:22 -0500

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Tuomas J. Lukka <address@hidden>        03/02/01 12:32:22

Modified files:
        doc/pegboard/buoydesign--tjl: peg.rst 

Log message:
        More design

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/buoydesign--tjl/peg.rst.diff?tr1=1.7&tr2=1.8&r1=text&r2=text

Patches:
Index: gzz/doc/pegboard/buoydesign--tjl/peg.rst
diff -u gzz/doc/pegboard/buoydesign--tjl/peg.rst:1.7 
gzz/doc/pegboard/buoydesign--tjl/peg.rst:1.8
--- gzz/doc/pegboard/buoydesign--tjl/peg.rst:1.7        Fri Jan 31 06:35:50 2003
+++ gzz/doc/pegboard/buoydesign--tjl/peg.rst    Sat Feb  1 12:32:22 2003
@@ -3,8 +3,8 @@
 =============================================================
 
 :Author:   Tuomas J. Lukka
-:Last-Modified: $Date: 2003/01/31 11:35:50 $
-:Revision: $Revision: 1.7 $
+:Last-Modified: $Date: 2003/02/01 17:32:22 $
+:Revision: $Revision: 1.8 $
 :Status:   Incomplete
 
 Goals: get the xupdf and pp functionality under one model.
@@ -19,7 +19,7 @@
     and use the boolean return value to determine whether
     regeneration is needed.
 
-    This also fixes the idea that a BuoyViewNode is really a single
+    This also fixes the idea that the *BuoyViewMainNode* is really a single
     view in a single VobScene.
 
 - Should we let keystrokes also not-regenerate the vobscene?
@@ -143,8 +143,8 @@
     Link.c = TransclusionLink.c + o;
 
 
-Implementation
---------------
+Interfaces
+----------
 
 Now, the picture gets clearer: the whole structure of the current buoy view
 should be *defined* by a single facade:
@@ -197,7 +197,7 @@
 
 The linkId passed to BuoyLinkListener must be unique for each node 
 and the identifies the link -- it must be the same in both directions.
-The previous invariant in code is an invariant which the BuoyViewNode interface
+The previous invariant in code is an invariant which these interfaces
 must obey::
 
     buoyviewnode1.renderMain(..., l);
@@ -218,5 +218,17 @@
 Matcher structure can separate left&right links and know which way
 
 
+The pluggable implementation
+----------------------------
+
+In this implementation of the BuoyViewMainNode and BuoyViewNodeType interfaces,
+the node and link types are pluggable. There are naturally some problems with
+full pluggability, due to the bidirectionality of the links: some node types
+will only match some other node types, etc.
+
+As the main example, consider the above case with ZZ cell nodes, PP canvases
+and scrollblocks. The ZZ cell nodes and PP canvases are both in ZZstructure
+and use cellviews so they can be handled by the same linking managers,
+but the scrollblocks cannot.
 
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]