Re: Organising the xwt namespace

Let's take button as an example.

The xwt.standard theme will probably be of the following structure:

<bevel id="outer">
    <bevel id="focus" form="null">
        <box id="icon" />
        <box id="spacer" />
        <box id="container />
    </bevel>
</bevel>

Now with this being in xwt.theme, if you want to differ from this, either
xwt.theme either has to allow the removal of the above boxen to make way for
a new box structure, or... ?  Force this structure on everybody else?

-----Original Message-----
From: David Crawshaw [mailto:[email protected]]
Sent: 02 April 2003 15:10
To: [email protected]
Subject: Re: [xwt-dev] Organising the xwt namespace



On Thursday, April 3, 2003, at 12:06  AM, Charles Goodwin wrote:
> I'm completely against having xwt.theme (as in the theme code that 
> custom
> themes would use) include a theme.  It'll not only make it more 
> difficult to
> code (you'd have to take into account boxes across multiple templates) 
> but
> it'd be confusing.  KISS.  Keep It Separate and Simple. :)

Not meaning to argue the point, but what do you mean 'boxes across 
multiple templates'? How would an implementation in xwt.theme make 
anything more complicated than it is now?

When you overlay() org.xwt.theme.<myfavorite>, on xwt.theme, it won't 
make a difference what's inside.

d


_______________________________________________
http://lists.xwt.org/listinfo/dev
_______________________________________________
http://lists.xwt.org/listinfo/dev