On 11 November 2011 23:13, Johannes Rasche <[email protected]> wrote:
> > > -------- 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 > <[email protected]><[email protected]> Antwort > an: [email protected] An: [email protected] > > as Igor mentioned yesterday it's useful for long texts. > > well, i said that its purpose to display different portions of same text in multiple morphs. For long texts, i really doubt that its uselful, because it doesn't scales well. > I would suggest, if the majority don't see the advantage of pred/succ, > to create a subclass > > Agreed. Right now , Pharo not using this feature in text editor(s). There is no need to have such complicated text composition, and i doubt it will arise. If someone would want to create a full-pledged text viewer/editor with multipage/multicolumn layout support, first thing what i would do is to use different model for text, not one which used in Text class. > 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<[email protected]> > >> <[email protected]> > >> 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 ;) > >>>> > >>> > >> > >> > > > > > > > -- Best regards, Igor Stasenko.
