This is an exaggerated comment, but... you know that nowadays most of the pages uses various MB on each load, for example just opening apple store downloads 2M, just click ipad goes up to 6M. So... em, hehe codespliting a 1MB uncompressed JS (probably around 300k compressed) which is going to be cached forever is not very good place to dedicate your effort ;). Obviously is just an opinion. But the monolithic approach with the pretty nice unused resources purge algorithm of GWT is even better now than 5 years ago (I remark the 'purger' because you cannot purge if you do not compile the whole app at once). And it even support code splitting if you goes up to various MB of JS.
On Friday, November 4, 2016 at 11:20:31 AM UTC+1, Ramesh S wrote: > > Hi, > > I am looking for some help on GWT code splitting. > > I have a very basic gwt - maven project, which have a few model classes > (Shape, Circle, Square, etc). > and I use *demo.html* to load the generated *<mymodule>.nocahce.js*. > to pass the inputs and do some computation and get the result back. > > Here the *nocache.js* contains the whole java script of the GWT stuff > also my java classes converted to javascript. > > Is it possible to have separate java script file for my java classes. ? > > Thanks > > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
