Re: Clarification of layout proposal

> > xwt.standard
> > xwt.widget
> > xwt.theme[.common]
> > xwt.lib[.common]
> 
> Under this model, there is no point in having xwt.widget. As far as I 
> can tell, it defeats the entire purpose of everything I've been trying 
> to say.

No it doesn't, you're just not being flexible in how you look at it.

> The original goal of the proposal was that users use xwt.widget, which 
> is a frontend for the stuff in xwt.theme. But xwt.theme is overlayed by 
> the specific theme. That way, a power developer can get a themed copy 
> of the backend interface by pointing to xwt.theme.
> 
> Lets say for a moment we separate the default theme from xwt.theme, 
> which I am completely fine with. We can put it in xwt.standard, or 
> org.xwt.themes.simple. Then we'd do this:
> 
> xwt.widget - preapplies - xwt.theme
> xwt.standard - overlays - xwt.theme
> xwt.standard - preapplies - xwt.lib
> 
> What advantage is there in killing the value of xwt.theme?

Ok.  You seem to be forgetting that for many of the widgets, there are two
versions.  1) the lib and 2) the themable.  Then, on top of that, you wanted
*flicks through hundreds of past mails* to take the preapplies out of the
themable and stick them in a separate 3rd set so that people could either
take the themable, preapplied widgets or for more specific cases (eg where
they don't want a button to be focusable) just take the themable version
without the preapplies.

You can't have this 3 tier separation and overlay() successfully without
making overlay() somewhat intelligent, in only 3 dirs.

If *insert your theme* overlays xwt.theme, how can the your theme xwts
preapply xwt.theme files?  That's the hurdle the original layout gave us, as
I've explained time and time again.  Themes preapplied xwt.standard,
xwt.theme() substituted out xwt.standard and xwt perpetuated itself into a
crash.  The old layout was 2 layers, xwt.standard and xwt.standard.lib, and
you want another preapply layer on top of this (which I agree with).  3
layers.  And then, to prevent the needed for xwt.overlay() being
intelligent, the 'default' theme must be in a 4th layer.

Basically, xwt.standard would overlay nothing...

<xwt>
    <import name="xwt.standard" />

    <static>
        // if you want to theme
        xwt.overlay( "xwt.standard", "org.xwt.themes.simple" );
    </static>
...
</xwt>

Also, instead of common, how's about 'abstract' as suggested by Rod.  It's
sounds good, it sounds techincal, and it's 2 syllables and shortish.
_______________________________________________
http://lists.xwt.org/listinfo/dev