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.

Reply via email to