[Gzz-commits] fenfire/docs/pegboard/canvas_text--mudyc peg.rst

[Matti Katila]

CVSROOT:        /cvsroot/fenfire
Module name:    fenfire
Changes by:     Matti Katila <address@hidden>   03/05/04 05:44:47

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

Log message:
        fixes towards a better peg

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

Patches:
Index: fenfire/docs/pegboard/canvas_text--mudyc/peg.rst
diff -u fenfire/docs/pegboard/canvas_text--mudyc/peg.rst:1.3 
fenfire/docs/pegboard/canvas_text--mudyc/peg.rst:1.4
--- fenfire/docs/pegboard/canvas_text--mudyc/peg.rst:1.3        Fri May  2 
20:56:59 2003
+++ fenfire/docs/pegboard/canvas_text--mudyc/peg.rst    Sun May  4 05:44:47 2003
@@ -5,8 +5,8 @@
 :Author:       Matti Katila
 :Date:         2003-05-02
 :Stakeholders: 
-:Revision:     $Revision: 1.3 $
-:Last-Modified: $Date: 2003/05/03 00:56:59 $
+:Revision:     $Revision: 1.4 $
+:Last-Modified: $Date: 2003/05/04 09:44:47 $
 :Type:         User Interface, Spatial canvas RDF structure, Text format
 :Status:       Incomplete
 
@@ -26,21 +26,6 @@
 Issues
 ------
 
-- If we generate rst to pdf does it break the 
-  xanalogical link doesn't it?
-
-    RESOLVED:
-    Yes, if we *replace* the text canvas with
-    page canvas. Currently idea is to use pdfs from outside 
-    and annotate those. So the question is why can't we 
-    build a new article from annotations and link xanalogically
-    the annotation canvas to pdf generated from it?
-
-    Actually this is out of scope of this peg.
-    This peg's purpose is to tell about additional structure to handle 
-    text easily in text canvases.
-
-
 - Would Nile like text editability be too complex for pp?
 
     RESOLVED:
@@ -48,6 +33,37 @@
     set by default. Paragraph thinking already solves much 
     of the current problems of pp text editability also.
 
+- If we have associated a node [foobar] and
+  someone likes to split it as a [foo], [ ], [bar].
+  What we do for the rdf propertys while splitting?
+
+    RESOLVED:
+    We do copy all propertys from [foobar] to [foo] and [bar],
+    except the property 'nextNode' which is set like:
+
+    Old: ::
+
+       [prev] --nextNode--> [foobar] --nextNode--> [next]
+
+
+    New: ::
+
+       [prev] --nextNode--> [foo] --nextNode--> [ ] -->
+ 
+          >>--nextNode--> [bar] --nextNode--> [next]
+
+- Why sentence hasn't words but nodes?
+
+    RESOLVED:
+    If one of the future goals is rst generated presentation
+    we need to be able to say where there are spaces.
+
+- What to do with emptys (spaces like [ ]) in rst generated view?
+    
+    RESOLVED:
+    That's the point, we don't show them but we do have to show them 
+    in text mode view.
+
 
 RST as a inspirer
 -----------------
@@ -66,7 +82,7 @@
 As discussed with Asko about rst like canvases he quite 
 fast informed me about Nile. After looking to Nile I
 needed to come back to design board. Yes, we absolutely
-need nodes or words, sentences and paragraphs as a primitives. 
+need nodes, sentences of nodes and paragraphs as a primitives. 
 
 
 What's it all about?
@@ -81,7 +97,50 @@
     - nodes are contained to canvas.
 
 Nodes' coordinates are generated because of they are additive to
-paragraph's coordinates.
+paragraph's coordinates. So, a node isn't spatially placed but a paragraph is.
+
+One sentence usually has words, numerals and such. We must also 
+count spaces to be included into sentences because we should 
+reach for real text editability when we really dominate the text buffer.
+So the following text ``This is a sentence.`` would be splitted to nodes
+marked by '[ ]': ::
+
+      1      2    3     4    5    6       7
+    [This], [ ], [is], [ ], [a], [ ], [sentence.]
+
+Now we are able to link any of the seven nodes with pp association.
+Of course we don't like even try to link empty - [ ] -nodes to anywhere but
+it would look very silly to link [foobar ] to somewhere. 
+Problems also occur if one adds a space and word after 'r'. 
+[foobar ] would have to be splitted and now [foobar] and [ ] would be linked!
+
+
+Changes to structure
+--------------------
+
+Current structure: ::
+
+    (Paper)  --PAPER.contains---> (A note)
+
+    (A note) --SPATIAL.coordsX--> literal
+    (A note) --SPATIAL.coordsY--> literal
+
+Proposal addition to this: ::
+
+    (Paper) --RST.beginParagraph--> (RST.Paragraph)
+
+    (RST.Paragraph) --SPATIAL.coordsX--> literal
+    (RST.Paragraph) --SPATIAL.coordsY--> literal
+
+    (RST.Paragraph) --RST.firstSentence--> (RST.Sentence)
+
+    (RST.Sentence)  --RST.nextSentence-->  (RST.Sentence)
+    (RST.Sentence)  --RST.nextNode-->      (A note)
+
+    (A note)        --RST.nextNode-->      (A note)
+
+Again, (A note)s' coordinates are generated because of they are 
+additive to RST.Paragraph's coordinates.
 
 
 Goal
@@ -97,12 +156,4 @@
 RST generating of text build up of the paragraphs placed on canvas.
 One issue would be how text format is handled and does this proposal
 approach it in different manner. 
-
-
-Irrelevant
-----------
-
-PDF generating from rst converted to latex. This would make FenPDF
-also as a article productive wholeness. Because of xanalogical suicide
-this is out of scope.