Re: One Last Description

Andrew Kohlsmith wrote:
> xwt.theme - documentation and stubs for THEME APIs
> xwt.theme.abstract - common behaviour code and box structures for 
> THEMES
> xwt.widget - documentation and stubs/preapplies for WIDGET APIs
> xwt.lib - code for widgets (i.e. x.t.a theme-independent stuff)
> xwt.lib.abstract - code for behaviours (x.t.a theme-independent stuff)
> xwt.standard is the standard (bare-bones) theme

I can't really provide any argument against this other than 
organisational.

However, we're still talking about slightly different things, as you 
have preapply xwt.widget.button in xwt.standard.button. This causes the 
cyclic mess you mentioned before, and I don't think this model calls 
for that.

xwt.widget.button - preapplies - xwt.theme.button, xwt.theme.focusable
xwt.theme.button - is just a stub
xwt.standard.button - preapplies - xwt.lib.button_functions, 
xwt.lib.button_layout
xwt.standard - overlays - xwt.theme

I have as much a problem with cyclic depdencies as you do, but what 
we're talking about on the wiki doesn't have this problem.

If you want a bare-bones theme in xwt.standard instead of xwt.theme, 
then I'm up for that. But we can't really have this xwt.standard.button 
preapplies xwt.widget.button. xwt.standard should be an implementation 
of the template package described in xwt.theme.

Also, I really would prefer some uniform naming scheme (as Adam has 
suggested on the wiki) rather than a separate directory for behavior 
code, but it's simply an organisational argument.

d


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