Re: widgets plan proposal

You have to bear in mind that the majority of people won't care about the
internal widget code.

They will simply use the widgets and theme them.  They want easy access to
1) the widget docs, 2) useful non-standard widgets (eg colorpicker, md5),
and 3) the super widgets (richtext editor, html etc).

What I'm trying to say is that it's not necessary to spread the standard/lib
and behaviour/lib in minimal directory names under xwt.  As long as you have
easy access to the above 3, only the widget developers care about the widget
code.  What's important is that they are laid out logically so that 1)
navigating them is easy and 2) navigating them is intuitive.  (They are 2
similar but different concepts.)

IMHO the xwt.theme, xwt.lib, xwt.widgets layout does not address the
priorities but rather gives the novice more to swallow when they are looking
for somewhere to start.
_______________________________________________
http://lists.xwt.org/listinfo/dev