Re: Widget Architecture

On Thursday, April 3, 2003, at 01:51  PM, Adam Megacz wrote:
>> http://zentus.com/widget-arch.pdf
>
> Uh, I really don't see why we need xwt.lib.theme, xwt.theme.common,
> and xwt.lib.common.  Can you give a concrete example (specific widget)
> where not separating these out would cause a problem?

Honestly, I can't see a reason for xwt.lib.[theme|common]. But Andrew 
and Charlie really like the idea. I'm hoping one of them can explain it 
to me. It was just a compromise I made because it doesn't actually 
limit the architecture.

I can see a reason for xwt.theme.common: Clear separation of the 
Behavior Templates from the Abstract Widgets. xwt.theme has to have all 
the templates from xwt.widget, plus about 7 more widgets, plus 7 
behavior templates. The numbers are starting to get big. But this 
really doesn't bother me either. I'm happy either way, as it's another 
one of those 'it doesn't kill the architecture' decisions.


>> - No theme in the xwt.* packages
>
> The only reason I'm against that is that if somebody forgets to call
> xwt.theme(), their UI renders in a totally wacked-out, bizarre manner,
> usually leaving them wondering "what the heck happened"?

Well I'd like to see xwt.* stand on its own, and I'd like to see a 
reference implementation in xwt.theme to help the documentation. But 
I'm compromising on this point, as it doesn't affect the overall 
architecture.

All that's really important to me is we have the two interfaces for 
developers, xwt.widget and xwt.theme, and we define a theme as: 'a 
package that completely implements the documented features in the 
xwt.theme package.'

d


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