File Structure

Just throwing around a possibility:

xwt.widget:
- button
- radio
- check
- text
- tree
- spin
- table

- cardpane
- grouppane
- scrollpane
- splitpane
- tabpane

- window
- dialog

- clickable
- focusable
- draggable (in the future)

xwt.theme: (from above, plus)
- tab
- bevel (should be managed automagically with xwt.widget.group)
- treeleaf
- cell
- bar
- bevel
- scroll (should we drop the *bar?)

xwt.lib: as required

There will be a few more things for the theme list, but I don't want to 
do that until the just before time comes to freeze the audit branch.

I got a little sick of our old names, which was a bit of a mishmash of 
other widget libraries. For some reason, we have a checkBox, but we 
also have a radioButton. I figured:
- everything is a box, so drop the *box suffixes
- check and radio are not really buttons
- what does edit edit? it's really a textbox, which can be edited. then 
we drop box -> a la text.

The rich text editor I'm working on would fit in as:

xwt.html.* - start from scratch rendering library
xwt.theme.richtext.* - themeable selection model and editor build on 
top of (preapplies) xwt.html
xwt.widget.richtext - simple rich text editor, with a menu child in it 
that can be put somewhere useful by the application (buttons for Bold, 
Italics, Underline, Font, Color, etc).

I really didn't want to start xwt.html from scratch, but I have a week 
coming up in which I'll put the preliminary support development, and 
hopefully I can justify my actions.

d


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