Organizing the xwt namespace
Rod Martin <[email protected]> Thu, 3 Apr 2003 09:48:24 -0500
| Newsgroups | gmane.comp.java.xwt.general |
|---|---|
| Organization | Benshaw |
| Message-ID | <[email protected]> |
Ok, as far as I can see, the only difference between David's suggestion and
Charlie's suggestion is in what stuff goes in which directory:
D's xwt.widget == C's xwt.widget
D's xwt.lib[.abstract] == C's xwt.lib[.abstract]
but
D's xwt.theme == C's xwt.standard (except that xwt.theme has theme docs and
xwt.standard does not)
D's xwt.lib.theme[.abstract] == C's xwt.theme[.abstract]
If implemented correctly, either setup will work.
In David's setup, org.xwt.theme.mytheme.somewidget preapplies stuff in
xwt.lib.theme (or for funky widgets, just xwt.lib). No
org.xwt.theme.mytheme.widget is preapplying anything in xwt.theme, so
xwt.overlay("xwt.theme", "org.xwt.theme.mytheme") won't cause the app to
crash.
In Charlie's setup, org.xwt.theme.mytheme.somewidget preapplies stuff in
xwt.theme (or for funky widgets, just xwt.lib). Since the overlay in this
setup is on xwt.standard (xwt.overlay("xwt.standard",
"org.xwt.theme.mytheme"), the app won't crash either.
Really, at this point, we're arguing about whether theme independent stuff
needs to go into xwt.lib.* or not. (Unless I'm missing something big.)
Personally, I think Charlie's setup is more intuitive, but let's all agree on
one thing, shall we?
Rod
_______________________________________________
http://lists.xwt.org/listinfo/dev