We have done some initial tests with code splitting, and it's working quite well. I don't know when it'll make it into the release, though - it will probably not be in 6.4, certainly in 7, maybe somewhere in between.
Code splitting is actually quite easy to implement due to the way Vaadin creates the GWT widgets, but we still want to work on some details: we want it to be quite flexible, while still easy to use, with sane defaults. We want the developer to be able to configure exactly what should be preloaded or on-demand, and perhaps also allow stuff to be loaded in the background when the user is idling. Anyway, code splitting is an awesome GWT feature that we've been waiting for - Vaadin is going to benefit from it soon. (BTW this has previously not been such a big issue, but now you can drag a whole lot of components into your project from the Directory, potentially super sizing the widgetset if the components happen to have a large clientside - code splitting will allow you to decide exactly what get's loaded when.) On Apr 1, 4:46 am, fonghuangyee <[email protected]> wrote: > After i studyVaadin, it is really good. > By the way,it is too bad becauseVaadinnot support code splitting. > Anyway i will keep a look atVaadin, thanks for your sharing. -- 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.
