Re: One Last Description

> > I don't want xwt.theme to have a theme in it -- I want xwt.theme to
> > have the theme code stubs and documentation that any theme needs to
> > implement to be considered a complete theme.  No theme.

> This will encourage developers to hardcode a call to xwt.theme() into
> their app.  That's bad.

How does that encourage that if xwt.standard is a simple theme that the engine 
themes to the native GUI theme whenever that gets done?

i.e. you don't include xwt.theme, you include xwt.standard.  No need for an 
xwt.theme() call then.

> It essentially means that you can't use an XWT gui to choose the
> initial theme, since the widget set is unusable before the first call
> to xwt.theme().

I dunno...  as I said you include xwt.standard and whenever you get around to 
making the engine automatically theme to the native theme, it just happens.  
no necessary xwt.theme() call on the call of the app designer.

Regards,
Andrew

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