Johannes Rasche Hagelberger Str. 56 10965 Berlin fon +49-30-315 66 820 mobil -49-1577 175 04 75 Anfang der weitergeleiteten E-Mail:

Von: Johannes Rasche <johannesrasche@mac.com> Datum: 11. November 2011 22:13:26 An: Pharo-project@lists.gforge.inria.fr Betreff: [Pharo-project] Fwd: Re: TextMorph: what is the purpose of predecessor/successor?

-------- Original-Nachricht -------- Betreff: Re: [Pharo-project] TextMorph: what is the purpose of predecessor/successor? Datum: Fri, 11 Nov 2011 15:34:47 +0100 Von: Johannes Rasche <johannesrasche@me.com>

Antwort an: johannesrasche@me.com

An: Pharo-project@lists.gforge.inria.fr

as Igor mentioned yesterday it's useful for long texts.

I would suggest, if the majority don't see the advantage of pred/succ, to create a subclass

Johannes

Am 11.11.11 14:43, schrieb Alain Plantec:

...

I forgot to say that I think we should simplify TextMorph as much as possible. I've already removed predecessor/successsor some time ago for my own textmorph fork. I open an isssue Alain

Le 11/11/2011 10:38, Igor Stasenko a écrit :

...

Thanks. Yes, i remember i seen this before, but i had no idea how it implemented.

On 10 November 2011 18:36, Alain Plantec<alain.plantec@yahoo.com> wrote:

...

Hi Igor, See the screenshot (Squeak 3.6). You can have several morphs editing the same text. Each morph containing its own part of the text. I guess predecessor ans successor are used in this context. Cheers

Alain

Le 10/11/2011 16:50, Igor Stasenko a écrit :

...

looks like the purpose is to make multiple morphs, displaying different (but adjacent) portions of one text..

But what i don't understand is what is the practical use of it? Is there an examples of such use of TextMorph(s)? As to me this looks a bit of over-enineering: morph represents a view of some model. Nothing prevents us from creating multiple different views of same model (a text in this case). And i don't get, what do we gain by letting them know about each other. If there is a need to have a coordination between views, i think it would be much simpler to have some centralized parent object/morph, which managing additional complexity related with such composition.

The functionality seems to be working: in text morph's halo, click on its menu , and there will be 'add predecessor' and 'add successor' menu items, which creating a fresh text morphs over same text and put it in ?hand?

i am clueless, what is purpose of this and whether it belongs to right place.. that's why i asking. (i would just throw it away ;)