Thanks Ben and Stef, the answer was in concordance with what i was thinking. CUIS already has the TextModel class, and the PluggableTextModel class. So together with the menu pragma builders of Pharo, they provide the foundations for the implementation you just nicely explained. Next week, once i finish writing something for my research, i will finish the initial port. And hopefully provide a working example of SMx in Pharo, applying the ideas here discussed. A somehow initial port, which can get expanded gradually, from the list of widgets we mentioned in previous emails: MorphTreeMorph, etc.. (and at a final stage Polymorph). Fernando pd: Alex, SMx is SimpleMorph, an older version of the cleaned up Morphic from the CUIS image. On Wed, Apr 6, 2011 at 6:19 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
YES!YES!YES! It is cool to see your impact on them. Excellent it will really helps bringing pharo IDE to the next level.
Stef
On Apr 6, 2011, at 2:11 PM, Igor Stasenko wrote:
On 6 April 2011 13:16, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Because once people are dependent and drug addict then they will spend time fixing it :)
No seriously this is mega hyper hyper important that we get     - solid scalable listMorph and treeMorph So the best way is to stress it.
The second answer is that nautilus is cool and needs tree :)
i second that. trees and lists are basic widgets which could be used for different means. So why we should limit ourselves and use some crappy lists to mimic tree, instead of using trees, and improving this widget and making it work well.
-- Best regards, Igor Stasenko AKA sig.