Just a comment. Following a discussion i recall having with Juan Vuletich, the same idea would apply for replacing Inheritance with composition for modeling geometry in Morphic.
Not having Morph -> RectangleMorph -> TextMorph , and pretty much all the subclasses of BorderedMorph. On Jan 31, 2010, at 9:30 PM, Stéphane Ducasse wrote: > Quizz > > What is the superclass of PopUpChoiceMorph ? > > > > the answer is below > > | > | > | > | > | > | > | > | > | > | > | > | > | > > . > . > . > . > . > . > . > . > . > V > > > > > StringMorph.... probably because it has a String displayed. > > We removed it with luc and noury. But this is just an example of mix between > inheritance > and composition we would like to avoid in the future > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
