Yes, sure I've seen this. You could easily load lots of code asynchronously using both approaches. But you will not remove dependencies in the compile time and main module will still inherit all other submodules, right? And if you change one module you have to recompile everything?
On Mar 25, 7:10 pm, kozura <[email protected]> wrote: > Yes! Fantastic new feature in GWT 2.0 called Code Splitting addresses > exactly this. See > here:http://code.google.com/webtoolkit/doc/latest/DevGuideCodeSplitting.html > > With a good code base and intelligent partitioning of separate pieces, > GWT will do all the dependency analysis and break off as much as > possible into chunks that are loaded when needed at runtime. I've > used this with great success to partition off large chunks of code not > needed at startup, but which might be used some point at runtime. Now > I can have as large an monolithic app as I want and not worry about > the load time getting ridiculous. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
