[UI] ToolBuilder

[Colin Putney]

On Sep 12, 2007, at 1:59 PM, Igor Stasenko wrote:

> On 12/09/2007, Jason Johnson <jason.johnson.081 at gmail.com> wrote:
>> On 9/12/07, tim Rowledge <tim at rowledge.org> wrote:
>>> The problem with 'decorators' or wrappers is that they need to
>>> implement all the methods of anything that they will wrap in  
>>> order to
>>> pass them on to the internal component. You could, of course, try to
>>> handle this by (ab)using doesNotUnderstand but the performance cost
>>> would be nasty. I think. Anyone got time to implement and time a  
>>> test
>>> harness?
>>
> Hmm.. i thought that decorations was exactly to avoid that?
> Suppose window having a frame as decoration. Since we interesting in
> operating with a window at first place in our model domain, we care
> less about it's frame decoration, title e.t.c which can be set while
> initializing and then handle some genereic UI events like
> resizing/moving.

Just a random thought here: Todd Blanchard did some neat work a few  
years ago on simplifying morphs and handling drawing through  
decorators. Neat stuff. There's a page about it on the wiki:

http://wiki.squeak.org/squeak/3186

Colin