RE: Organising the xwt namespace

Yes, but...

org.xwt.themes.monopoly.button preapply xwt.widgets.button which preapplies
xwt.theme.button which preapplies xwt.lib.button (altho xwt.lib.button
probably won't exist), and that's where this falls apart.

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



On Thursday, April 3, 2003, at 12:25  AM, Charles Goodwin wrote:
> 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?

But your overlaying something new on top of it. theme()/overlay() 
doesn't apply templates on top of each other, it chooses the first 
template it finds in the overlay stack.

xwt.theme('xwt.theme', 'org.xwt.theme.monopoly')

Now when someone requests xwt.theme.button, they get 
org.xwt.theme.monopoly.button instead. It doesn't matter what weird box 
structure goes into xwt.theme.button.

d


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