Re: Organising the xwt namespace

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

Yes

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

This would only happen if we put a theme in xwt.theme. Otherwise, 
xwt.theme would be empty.

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

lib.button probably would exist, and would hold what you think should 
be in theme.button.

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

There's a problem right here. If monopoly.button preapplies 
widget.button, but the user is supposed to use widget.button as their 
basic interface, how do they get the theme? They can't overlay monopoly 
over widget, because then monopoly would be preapplying itself.

I don't think what your suggesting works. It's definitely not what I've 
been proposing, and not what Adam wrote up on the wiki.

> 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.

Yes, this part works. Due to the overlay, what actually gets preapplied 
is not theme.button and theme.clickable, but monopoly.button and 
monopoly.clickable.

> fictionaltheme.button wants only basic button code and a different 
> focus
> model so, in reality, preapplies lib.common.clickable and
> fictionaltheme.focusable.

This part works.

I'm off to bed now. Have a test tomorrow.

d


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