Re: Organising the xwt namespace

I forgot to add:

xwt.widget.button - how the average button user would use button
xwt.theme.button - how to implement button in a theme

-----Original Message-----
From: Charles Goodwin [mailto:[email protected]]
Sent: 02 April 2003 15:55
To: '[email protected]'
Subject: Re: [xwt-dev] Organising the xwt namespace


Okay, I'll elaborate.  This was how I understood it to work (and indeed how
I described it in the email proposing the layout inc common):

widget.button preapplies; specifically clickable, focusable, and
theme.button

theme.button holds common button behaviour; in this case enter to activate,
and would preapply lib.button if it existed

lib.button (which actually doesn't exist because all lib behaviour is
clickable / focusable)

monopoly.button is a typical button, so it would preapply widgets.button and
take all the behaviour with it.

monopoly.tableheader (fictional example) wants to look like a button, but
doesn't want to be focusable, so it preapply theme.button and
theme.clickable.

fictionaltheme.button wants only basic button code and a different focus
model so, in reality, preapplies lib.common.clickable and
fictionaltheme.focusable.
_______________________________________________
http://lists.xwt.org/listinfo/dev