Re: Organising the xwt namespace

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

How do you figure that?  xwt.theme would be all the almost generic theme
traps.  Things like _keypress/_keyrelease, and layout box traps (_layoutbox
= function() { handle it }).  It'd be the most full dir of them all.

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

Your idea of what goes in lib is very different from mine.  Mine certainly
doesn't include that based on an assumed preapply (_keypress / _keyrelease).

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

Well, since the user would over xwt.standard, not xwt.widget, this is not a
problem.

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

I spent hours upon hours battling with the (no offense) crap original
layout.  Things like xwt.theme( "xwt.standard", "org.xwt.themes.simple" )
crashing xwt cos I was preapply stuff from standard.  That's why we moved
stuff into sub directories in the first place.  (Monopoly escaped this by
preapply xwt.standard.* <- the .* making the difference.  But this was lame,
so we moved it.)

The point is, I'm pretty sure this would work since I've spent that much
time working with xwt of late, especially working around it's problems.
You're just thinking of how it wouldn't work with your layout - of course it
wouldn't!  It's slightly different!

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

I'll wait to hear from you tomorrow then. :)

One last thing though.

Where would you go for widget documentation?  And where would you go for
theme implementation documentation?  (Here's a clue, in your proposed
layout, for widget documentation you'd go to xwt.theme and for theme impl
documentation you'd go to xwt.widget.)
_______________________________________________
http://lists.xwt.org/listinfo/dev