That's a pretty good idea.  I was thinking of an incremental approach that
eventually leads up to the concept of "skins".

  - Steve

Jason McVay wrote:

> i've only briefly peered at SystemWindow, but i did notice that it could
> benefit from have the titlebar code factored out into a class of its own. it
> would make things definitely prettier (read as 'easier to grope'). is there
> reason why the titlebar code has to be stuffed in the SystemWindow class?
>
> curiously questioning,
> jason
> ----------
> >From: "Stephan B. Wessels" <stephan.wessels at sdrc.com>
> >To: squeak at cs.uiuc.edu
> >Subject: SystemWindow>>initialize
> >Date: Thu, Dec 2, 1999, 15:15
> >
>
> > It looks like it's pretty common for folks to extend or enhance the
> > initialize method
> > in SystemWindow.  I wonder if we could benefit from some better factoring
> > of the code
> > in there so that extensions could be easier to swap out?
> >
> > For instance,
> >
> > add a method which answers the stripes (probably have to do something to
> #extent
> > method too, I think) and then move the code there.
> >
> > add a method which answers the label and move that code.
> >
> > add a method to add the collapse button and move that code there.  Just like
> the
> > close box and menu control methods do now.
> >
> > we could even add a method to add special features and leave that stubbed out
> by
> > default.
> >
> > Just some ideas,
> >
> >  - Steve