[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 06:18:30

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

Log message:
        please: add issues, raise discussion.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/fenfire/docs/pegboard/content_handler--mudyc/peg.rst?rev=1.1
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/fenfire/docs/pegboard/nodeview_abstract--mudyc/peg.rst.diff?tr1=1.7&tr2=1.8&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.7 
fenfire/docs/pegboard/nodeview_abstract--mudyc/peg.rst:1.8
--- fenfire/docs/pegboard/nodeview_abstract--mudyc/peg.rst:1.7  Fri Apr  4 
05:09:22 2003
+++ fenfire/docs/pegboard/nodeview_abstract--mudyc/peg.rst      Fri Apr  4 
06:18:30 2003
@@ -4,8 +4,8 @@
 
 :Author:   Matti Katila
 :Stakeholders: Matti Katila
-:Last-Modified: $Date: 2003/04/04 10:09:22 $
-:Revision: $Revision: 1.7 $
+:Last-Modified: $Date: 2003/04/04 11:18:30 $
+:Revision: $Revision: 1.8 $
 :Status: Incomplete  
 
 
@@ -21,9 +21,9 @@
  
        - xyz implicates Text, Image, Sound and Page etc.
 
-Another PEG will explain the enfilade handling of nodes.
-This PEG only tells how node is to be placed knowning
-nothing about the content.
+The content_handler--mudyc PEG will explain the enfilade 
+handling of nodes. This PEG only tells how node is to be 
+placed knowning nothing about the content.
 
 
 
@@ -37,8 +37,6 @@
 In the past we did usually have only text to show for user.
 Today we have more media types: pagespans and images at least.
 The View framework has been designed too much for text only. 
-Text based design is also very deeply seen in Space where we have 
-*VStreamNodeTexter* but that's an another story. 
 Although text is the most common view media we should 
 easily be able to show any content in nodes.
 
@@ -126,7 +124,7 @@
 Changes
 -------
 
-I propous several interfaces to be implemented by suitable content state 
handler: 
+I suggest several interfaces to be implemented by suitable content state 
handler: 
 
 ::
 
@@ -142,6 +140,7 @@
 
    public interface PageState {
       void setBackgroundTexVisible(boolean b);
+      boolean isBackgroundTexVisible();
    }      
 
 
@@ -172,7 +171,7 @@
 Changes
 -------
 
-When NodeView has a new node to place it should mention it to ViewContext.
+When NodeView has a new node to be placed it should mention it to ViewContext.
 
 So ViewContext should implement the following interface:
 
@@ -210,7 +209,7 @@
     public abstract class NodeView implements NodeContent {
 
         // Space/FenfireContext
-        // for asking content - see the PEG followed be this PEG ;)
+        // for asking content - see the PEG content_hanler--mudyc followed be 
this PEG
         protected Space/FFC/Fen foo;
 
         // ViewContext - see 3)
@@ -221,12 +220,12 @@
         protected RDFNode current;
 
         // correct state/context handlers.- see 2) and 3)
-        // and see the PEG followed by this PEG.
+        // and see the PEG content_hanler--mudyc followed by this PEG.
         public TextHandler text;
         public ImageHandler image;
         public PageHandler 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.
+It's important that all 1), 2) and 3) are combined in NodeView because it's so 
often 
+used. Nobody wants to use continuos type casting with long interface names 
with Java.