On Mar 14, 2010, at 8:41 PM, Stéphane Ducasse wrote:
I building a new TextMorph, in the context of porting Cuis Editors.
I'm having problems understanding some behavior of TexMorph,
1. Whats the purpose of predecessor and successor in TextMorph?
is it not to bind to the next one and get the text flow as in the cool squeak demo.
where can is see this demo? , i think that having pred and suc made the code more complicated.
2. Why does the paragraph needs to be lazily initialized.
Im my implementation of TextMorph i have neither and i don't see a good reason to add them.
Fernando
Fernando I would suggest to publish the code and that we see. With Morph I have the impression that a lot have to be reconsidered.
I cleanup a lot of stuff out of TextMorph, into NewTextMorph.
Stef
Yes, during this Pharo Sprint we worked on a EntryFieldMorph, NewTextMorph and CodeMorph, that respectivly use SimpleEditor, TextEditor and SmalltalkEditor ( from CUIS). I'll make a couple of tests tomorrow and publish the SLICE. Fernando
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project