On Mar 31, 2011, at 10:50 AM, Stéphane Ducasse wrote: >> >> 2) 4) Regarding TextModel and subclasses such as CodeProvider and >> Browser in CUIS: so it means that hierarchy wouldn't be needed at all >> in Pharo. At least Nautilus must have a model for the text ? In CUIS >> the root class is called TextModel , in Pharo 1.3 is called >> StringHolder. I propose moving this discussion on another thread. >> Maybe Benjamin could clarify this? > > benjamin will let us know.
I think that the text should be handled by a Browser but by the TextMorph, or you will have the same ugly hierarchy than StringHolder, when a Model/View are badly mixed and where each tool that manage source code inherits from it, without using properly inheritance ... IMHO, it should be orthogonal to that, and should be "pluggable" in each tool which need it. Right now for Nautilus, I have borrowed only 3-4 methods from StringHolder/CodeHolder/Browser, almost all expected behavior is provided by PluggableTextMorph Ben
