I just worry about GWT itself. Google may kill GWT some day. Our
project heavy uses it:(.
It doesn't release any new major version since last Dec. Although
there is 2.1m2 released, I test it and found it is far more from final
release. One year is for a major release, can we call it as an active
It is not new questions in this group. But I face a new problem in
2.0M2 as SerializationPolicy logic is changed. I know GWT will put
serializition class into SerializationPolicy whitelist. Before 2.0, I
create a dummy method which hold all classes I want to pass to client
side but they are not in
traffic
> > amounting to a a total network xfer of only 4k!!! ( as reported by
> > firebug )
>
> > On Nov 13, 2:14 pm, hazy1 wrote:
>
> > > Our code size, uncompressed is several megabytes. We compress and
> > > cache it (both on the client and on the serve
Finally, I chop one class from my bloat code by code splitting
function. The class is a dialog box, about 100 lines code.
Unfortunately, the result looks funny:
Before splitting: Full code size: 868323
After splittting: Initial download size: 871391 Full code size:
874615
It looks Gwt.runAsync
I try 2.0m2 soyc and code splitting. It looks soyc doesn't need 2
steps. After add -soyc option in GWT compiler, it outputs HTML format
files. Is it true?
But after I add GWT.runSync(), the soyc doesn't make any change. My
code size grows a little bit rather than reducing. Do I need add some
com
I am very excited for code split feature on Gwt 2.0 as the HTML code
size after compiled already bloats to 850k. I give a quick try but it
looks not work like a breeze. I know I have to do more research. I
don't use lots of third party libraries, actually, only 2 libraries:
GWT-DND, GWT-LOG. My GWT
