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.
