[UI] ToolBuilder

Gary Chambers gazzaguru2 at btinternet.com
Wed Sep 12 16:54:32 UTC 2007


That's the jist, a generic way would leave little control and/or potential
conflicts though...

> -----Original Message-----
> From: ui-bounces at lists.squeakfoundation.org 
> [mailto:ui-bounces at lists.squeakfoundation.org] On Behalf Of 
> Igor Stasenko
> Sent: 12 September 2007 5:42 pm
> To: Squeak's User Interface
> Subject: Re: [UI] ToolBuilder
> 
> 
> On 12/09/2007, Gary Chambers <gazzaguru2 at btinternet.com> wrote:
> > I expect supporting the scrolling would have been more work and not 
> > benefit from improvements to the ScrollPane class. 
> Delegation "should" 
> > have looked straightforward... Better to compose than rewrite with 
> > potential inconsitencies!
> >
> 
> Aha, so it looks like a composition of different 
> morphs/interfaces. It seems done only for bringing textMorph 
> interface to the front, so users of PluggableTextMorph can 
> deal with text without traveling through morphs hierarchy 
> (ScrollPane->TransformMorph->TextMorph).
> 
> Interesting, how this can be achieved in more clean and 
> generic way? I'm just thinking of using traits. Suppose we 
> have a trait like "PluggableText", which relies on single 
> message 'self textMorph' and exposes TextMorph interface to 
> class where trait is used. Then we can easily have interface 
> compositions like ScrollPane + TextMorph or AnythingElse + TextMorph.
> 
> -- 
> Best regards,
> Igor Stasenko AKA sig. _______________________________________________
> UI mailing list
> UI at lists.squeakfoundation.org 
> http://lists.squeakfoundation.org/mailman/listinfo/ui
> 



More information about the UI mailing list