What I objected to at the time (I don't know if this is still the case) was the
complex HTML structures wrapped around a bit of text. Something like:
<div class="foo"><div class="bar"><div class"whiz"><div class="bang">Some
text.</div></div</div></div>
I can understand the need for multiple <div> elements - so that you can layer
effects (due to CSS limitations). But why do they all need to have their own
class? The only one needed is "foo" - you can style the contained <div>
elements with CSS descendant selectors.
-Adrian
--- On Fri, 5/1/09, Adam Heath <doo...@brainfood.com> wrote:
> From: Adam Heath <doo...@brainfood.com>
> Subject: Re: Microsoft NAV look and feel
> To: dev@ofbiz.apache.org
> Date: Friday, May 1, 2009, 2:13 PM
> Adrian Crum wrote:
> > Someone suggested GWT two years ago and I took a look
> at
> > it. From what I recall, it requires some complicated
> and
> > sometimes convoluted markup in order to get the
> desired
> > effects.
>
> I've got gwt startup code that scans the page document
> for
> class="Foo", and converts them to GWT widgets on
> the fly. But since
> it has to handle any possible widget, the compiled output
> tends to
> include *all* of GWT; almost nothing can be optimized out.
> This tends
> to give a 300k javascript file, or larger/smaller,
> depending on
> obfusication.
