Re: [Fresco-devel] Getting the basics straight, was: Text styles/cloning graphics
Stefan Seefeld <[email protected]>
| Newsgroups | gmane.comp.video.fresco.devel |
|---|---|
| Message-ID | <[email protected]> |
Tobias Hunger wrote: > I further assumed this graphic is caching the situation of the TextBuffer in > the scenegraph (using boxes, glue, glyphs, etc.) to avoid the overhead of > redoing the linebreaking and layout on each rendering pass. what has 'the situation of the TextBuffer' to do with linebreaking and layout ? > That overhead is > the reason why TeX runs non-interactive and why most graphical TeX editors > use some way more simple algorithmns then TeX itself. > > Can we all agree on these two basic assumptions? no. I'm all for good and fine-tuned caching where appropriate, but the correctness of the server's behavior mustn't depend on it. Read: caching is an implementation detail. > PS: What I tried to describe with the trees in my original mail was this > 'cached' form. aaaaah. But then we are not talking about graphics any more. The caching composite object (a paragraph, say) knows a good deal more about the objects it caches, and thus all the other questions you raised such as whether or not to add 'clone' methods doesn't target the 'Graphic' interface but something else. Stefan