Gary, Dumb question: is it enough to add it to TEasilyThemed? There is a refactoring opportunity, if only in the form of a helper method that takes the morph class to use and otherwise "says it once" about the other aspects. At least I *think* that's the case. One disappointing thing I just found/re-discovered: PluggableMultiColumnListMorph expects a collection of collections by column, not by row :( I have already taken some license with models, and this will make it harder to get right. I will try a simple adapter to produce the collection of columns on the fly. Better ideas are welcome. The Dolphin triad I am trying to emulate is a list of objects, each of which has multiple aspects presented across a row. In Dolphin, it is a little inflexible, but fast and very useful. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Gary Chambers [gazzaguru2@btinternet.com] Sent: Friday, June 10, 2011 12:05 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Polymorph: PluggableMultiColumnListMorph vs.PluggableListMorph Currently there are no TEasilyThemed helpers for mulit column lists. Please add! The method signatures should include parameters for each thing that is expected to be be set up (to encourage completeness of ui experience). Regards, Gary ----- Original Message ----- From: "Schwab,Wilhelm K" <bschwab@anest.ufl.edu> To: <Pharo-project@lists.gforge.inria.fr> Sent: Friday, June 10, 2011 4:45 PM Subject: [Pharo-project] Polymorph: PluggableMultiColumnListMorph vs.PluggableListMorph Gary, all, I just ran into a question: among all of the #newList* methods, is there a good way to refer to a particular subclass? Since these methods ultimately just create a morph, I am doing that with a little hard coding of some options. Is there a better way? Bill