/[fenfire]/fenfire/docs/pegboard/canvas_text--mudyc/peg.rst
ViewVC logotype

Diff of /fenfire/docs/pegboard/canvas_text--mudyc/peg.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.3 by mudyc, Sat May 3 00:56:59 2003 UTC revision 1.4 by mudyc, Sun May 4 09:44:47 2003 UTC
# Line 26  these three circumtances for our own bes Line 26  these three circumtances for our own bes
26  Issues  Issues
27  ------  ------
28    
 - 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.  
   
   
29  - Would Nile like text editability be too complex for pp?  - Would Nile like text editability be too complex for pp?
30    
31      RESOLVED:      RESOLVED:
# Line 48  Issues Line 33  Issues
33      set by default. Paragraph thinking already solves much      set by default. Paragraph thinking already solves much
34      of the current problems of pp text editability also.      of the current problems of pp text editability also.
35    
36    - If we have associated a node [foobar] and
37      someone likes to split it as a [foo], [ ], [bar].
38      What we do for the rdf propertys while splitting?
39    
40        RESOLVED:
41        We do copy all propertys from [foobar] to [foo] and [bar],
42        except the property 'nextNode' which is set like:
43    
44        Old: ::
45    
46           [prev] --nextNode--> [foobar] --nextNode--> [next]
47    
48    
49        New: ::
50    
51           [prev] --nextNode--> [foo] --nextNode--> [ ] -->
52    
53              >>--nextNode--> [bar] --nextNode--> [next]
54    
55    - Why sentence hasn't words but nodes?
56    
57        RESOLVED:
58        If one of the future goals is rst generated presentation
59        we need to be able to say where there are spaces.
60    
61    - What to do with emptys (spaces like [ ]) in rst generated view?
62        
63        RESOLVED:
64        That's the point, we don't show them but we do have to show them
65        in text mode view.
66    
67    
68  RST as a inspirer  RST as a inspirer
69  -----------------  -----------------
# Line 66  Nile as a inspirer Line 82  Nile as a inspirer
82  As discussed with Asko about rst like canvases he quite  As discussed with Asko about rst like canvases he quite
83  fast informed me about Nile. After looking to Nile I  fast informed me about Nile. After looking to Nile I
84  needed to come back to design board. Yes, we absolutely  needed to come back to design board. Yes, we absolutely
85  need nodes or words, sentences and paragraphs as a primitives.  need nodes, sentences of nodes and paragraphs as a primitives.
86    
87    
88  What's it all about?  What's it all about?
# Line 81  This proposal is all about: Line 97  This proposal is all about:
97      - nodes are contained to canvas.      - nodes are contained to canvas.
98    
99  Nodes' coordinates are generated because of they are additive to  Nodes' coordinates are generated because of they are additive to
100  paragraph's coordinates.  paragraph's coordinates. So, a node isn't spatially placed but a paragraph is.
101    
102    One sentence usually has words, numerals and such. We must also
103    count spaces to be included into sentences because we should
104    reach for real text editability when we really dominate the text buffer.
105    So the following text ``This is a sentence.`` would be splitted to nodes
106    marked by '[ ]': ::
107    
108          1      2    3     4    5    6       7
109        [This], [ ], [is], [ ], [a], [ ], [sentence.]
110    
111    Now we are able to link any of the seven nodes with pp association.
112    Of course we don't like even try to link empty - [ ] -nodes to anywhere but
113    it would look very silly to link [foobar ] to somewhere.
114    Problems also occur if one adds a space and word after 'r'.
115    [foobar ] would have to be splitted and now [foobar] and [ ] would be linked!
116    
117    
118    Changes to structure
119    --------------------
120    
121    Current structure: ::
122    
123        (Paper)  --PAPER.contains---> (A note)
124    
125        (A note) --SPATIAL.coordsX--> literal
126        (A note) --SPATIAL.coordsY--> literal
127    
128    Proposal addition to this: ::
129    
130        (Paper) --RST.beginParagraph--> (RST.Paragraph)
131    
132        (RST.Paragraph) --SPATIAL.coordsX--> literal
133        (RST.Paragraph) --SPATIAL.coordsY--> literal
134    
135        (RST.Paragraph) --RST.firstSentence--> (RST.Sentence)
136    
137        (RST.Sentence)  --RST.nextSentence-->  (RST.Sentence)
138        (RST.Sentence)  --RST.nextNode-->      (A note)
139    
140        (A note)        --RST.nextNode-->      (A note)
141    
142    Again, (A note)s' coordinates are generated because of they are
143    additive to RST.Paragraph's coordinates.
144    
145    
146  Goal  Goal
# Line 98  RST generating of text build up of the p Line 157  RST generating of text build up of the p
157  One issue would be how text format is handled and does this proposal  One issue would be how text format is handled and does this proposal
158  approach it in different manner.  approach it in different manner.
159    
   
 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.  
   

Legend:
Removed from v.1.3  
changed lines
  Added in v.1.4

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26