Re: [Pharo-project] TextMorph: what is the purpose of predecessor/successor?
On Nov 10, 2011, at 12:51 PM, Igor Stasenko wrote:
looks like the purpose is to make multiple morphs, displaying different (but adjacent) portions of one text..
In the orginal 2.0 Squeak image there was a demo that demonstrated text filling morphs, with the text flowing between multiple ones. It is likely that it has never been used outside of this Demo. The idea was that morphs could be the building blocks of a text layout system like we see in Pages or Word (or better example FrameMaker). So if you want to have two paragraphs on one page, put two textmorphs and let the text flow beteen them. No model, the morphs are the model and the view at the same time. The question is if that is really realistic to build a Rich Text editor that way?
(i would just throw it away ;)
Yes. Marcus -- Marcus Denker -- http://marcusdenker.de
On 10 November 2011 17:18, Marcus Denker <marcus.denker@inria.fr> wrote:
On Nov 10, 2011, at 12:51 PM, Igor Stasenko wrote:
looks like the purpose is to make multiple morphs, displaying different (but adjacent) portions of one text..
In the orginal 2.0 Squeak image there was a demo that demonstrated text filling morphs, with the text flowing between multiple ones.
It is likely that it has never been used outside of this Demo.
The idea was that morphs could be the building blocks of a text layout system like we see in Pages or Word (or better example  FrameMaker).
So if you want to have two paragraphs on one page, put two textmorphs and let the text flow beteen them. No model, the morphs are the model and the view at the same time.
The question is if that is really realistic to build a Rich Text editor that way?
I don't think so. As i said before, Text (class) model is a very limited and don't scales for big texts (multiple pages etc). Because if you imagine you editing 300kb text (book), any operation like insertion of a single character will require copying 300 thousands of characters into a new space holder. IMO Text is good for a couple lines of text (like smalltalk code). But for something bigger, like Word it should be completely different and require completely different approach and modelling.
(i would just throw it away ;)
Yes.
    Marcus
-- Marcus Denker -- http://marcusdenker.de
-- Best regards, Igor Stasenko.
participants (2)
-
Igor Stasenko -
Marcus Denker