*ListMorphs

Daniel Vainsencher danielv at netvision.net.il
Mon May 5 18:09:53 UTC 2003


Sean Charles <bibbers at onetel.net.uk> wrote:
> > transformer object that can be sent a domain object, and produces an
> > appropriate morph. This fixes both the "recieves only strings" and the
> > "displays only string morphs" problems.
> >
> 
> Shouldn't / Wouldn't it be better to make the domain objects responsible 
> for this? The rule is already in place as a lot of objects understand 
> messages like asString, asColor, asXYZ etc.

Depends. For a small hack, its the simplest thing that could possibly
work. If you intend to reuse the domain object in different UIs (never
mind in different applications, different Smalltalk dialects...), the
heat increases to move that responsibility somewhere else.

> I am a great fan and 'massive respect' is due to Morphic but sometimes it 
> is such a drag, literally, with big lists. Yeah, sure, download Lex's 
> patch etc etc but that's going to put off beginners. It (Morphic in 
> general, PLM in particular) needs to be a lean mean list machine out of 
> the box to gain credibility.

You're right, the solution is not for me to tell you to "download Lex's
patch". The solution is for people in the community to review it
seriously, decide if it is the simplest that could possibly work (or fix
it or offer alternatives), and then convince a Harvester it should be an
ENHancement, not a SM entry. 

And then I can tell you to "get 3.6" ;-)

Daniel



More information about the Squeak-dev mailing list