Re: One Last Description

David Crawshaw <[email protected]> Fri, 4 Apr 2003 09:07:16 +1000
Newsgroups gmane.comp.java.xwt.general
Message-ID <[email protected]>
On Friday, April 4, 2003, at 04:40  AM, Adam Megacz wrote:
> Does your proposal differ substantially from
> http://wiki.xwt.org/Wiki.jsp?page=PNGWA ?

Not at all. It just seemed to me that every time I described it, it got 
misinterprited. So I wrote it up with lots of redundancy in it.

After some sleep, I would suggest the sticking point is the number of 
tiers for xwt.lib. Some of the redesigned widgets in the audit have a 
new step in them, which I really don't believe is necessary. I 
understand it's a little hard to accept that point of view, so I'll 
prove it. I just need a little time to build an example.

However, in the mean time the best solution would be what you just 
suggested:

xwt.lib.scrollbar_layout
xwt.lib.scrollbar_functions

(this is all assuming the xwt.widget > xwt.theme > xwt.lib model from 
the wiki page)

Not all of these widgets have this secondary separation or need it. But 
this would be a good way to put it into the library.

Now we're back to the situation of is there any merit in putting a 
theme in xwt.theme.

It would make the themes simpler. If the default implementation in 
xwt.theme simply implemented the defaults from the lib, than themes 
which follow the standard model wouldn't have to replace standard 
templates. Less templates in a theme definitely makes it simpler to 
manage, and simpler to create.

Ie, if xwt.theme.focusable preapplied xwt.lib.focusable_functions and 
xwt.lib.focusable_layout, then you would not need 
org.xwt.theme.monopoly.focusable.

d


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