[Gzz-commits] fenfire/docs/pegboard/nodeview_abstract--mudyc ...

[Matti Katila]

CVSROOT:        /cvsroot/fenfire
Module name:    fenfire
Changes by:     Matti Katila <address@hidden>   03/04/04 02:48:08

Modified files:
        docs/pegboard/nodeview_abstract--mudyc: peg.rst 

Log message:
        enough for now.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/fenfire/docs/pegboard/nodeview_abstract--mudyc/peg.rst.diff?tr1=1.5&tr2=1.6&r1=text&r2=text

Patches:
Index: fenfire/docs/pegboard/nodeview_abstract--mudyc/peg.rst
diff -u fenfire/docs/pegboard/nodeview_abstract--mudyc/peg.rst:1.5 
fenfire/docs/pegboard/nodeview_abstract--mudyc/peg.rst:1.6
--- fenfire/docs/pegboard/nodeview_abstract--mudyc/peg.rst:1.5  Fri Apr  4 
02:14:52 2003
+++ fenfire/docs/pegboard/nodeview_abstract--mudyc/peg.rst      Fri Apr  4 
02:48:08 2003
@@ -4,8 +4,8 @@
 
 :Author:   Matti Katila
 :Stakeholders: Matti Katila
-:Last-Modified: $Date: 2003/04/04 07:14:52 $
-:Revision: $Revision: 1.5 $
+:Last-Modified: $Date: 2003/04/04 07:48:08 $
+:Revision: $Revision: 1.6 $
 :Status: Incomplete  
 
 
@@ -14,9 +14,10 @@
 
 This PEG includes three abstract which are
 
-    - Node content ('NodeView')
+    - Node content ('NodeContent and first definition of NodeView')
     - Node content state ('xyzState')
     - Node content with view context ('xyzContext')
+    - My proposal for abstract NodeView 
  
        - xyz implicates Text, Image, Sound and Page etc.
 
@@ -67,8 +68,9 @@
       }
    }
 
-I propous that we abstract ViewContext away and let 
-someone else to handle the view context. 
+I suggest that we abstract ViewContext away and let 
+someone else to handle the view context['3)']. 
+Now, make a new interface from the rest:
 
 ::
 
@@ -83,8 +85,8 @@
 Note:
    - **Very important thing** is that we don't know anything
      about the content. We can only assume what an enfilade includes. 
-     That's why I like to propouse additional methods to NodeContent 
-     interface which would be:
+     That's why I like to suggest additional methods to the interface
+     which would then be:
 
 ::
 
@@ -144,7 +146,7 @@
 
 
 These would be easily called from NodeView public attributes, i.e.,
-nodeview.text.setColor(Color.red); or 
nodeview.pagespan.setBackgroundTexVisible(false);
+nodeview.text.setColor(Color.red); or 
nodeview.page.setBackgroundTexVisible(false);
 
 
 
@@ -158,7 +160,7 @@
 View context isn't very easy task. When you place a node it's correct time to 
ask from
 view context if it has plans for current node. View context might want to set 
 cursor offset, pagespan view coordinates or it might want to set text's 
-color more important by reddishing for example.
+color more important by reddishing it for example.
 
 
 Issues
@@ -193,4 +195,37 @@
         void setViewCoords(float x, float y);
         float[] getViewCoords();
     }
+
+Of course ViewContext can change also states, i.e., text color and font, 
defined in the '2)'.
+
+
+
+4) NodeView
+===========
+
+My proposal for NodeView:
+
+::
+
+    public abstract class NodeView implements NodeContent {
+
+        // Space/FenfireContext
+        // for asking content - see the PEG followed be this PEG ;)
+        protected Space/FFC/Fen foo;
+
+        // ViewContext - see 3)
+        protected ViewContext viewContext;
+
+        // Current node - see 3)
+        // NodeView places nodes one by one.
+        protected RDFNode current;
+
+        // correct state/context handlers.- see 2) and 3)
+        public TextContextState text;
+        public ImageContextState image;
+        public PageContextState page;
+    }
+
+It's important that all 1), 2) and 3) are combined in NodeView because it's so 
often used.
+Noone wants to use continuos type casting with long interface names.