Comment by m.zdila: Hello.
This is certainly a nice feature, but one not requiring a monolithic compile would be that just great. Our application is built on top of OSGi. When a new module is added a new menu item appears in the GUI to access that module GUI (under different URL). Currently we must compile each OSGi module with the common "Workspace" library project and so the common Workspace part is duplicated over the modules and so needs to be loaded together with each module code. This is because of the monolithic build. Much nicer would be a separate Workspace module that just lazy-loads its (OSGi based) dynamic view modules on demand (menu item clicks). This way there would be no page reload (= the same URL), because the Workspace (header, menu, footer, common code) doesn't need to be reloaded. Is there any plan to make possible to do it like this? I think I ask for the same as mirceade does. Thanks in advance. For more information: http://code.google.com/p/google-web-toolkit/wiki/CodeSplitting --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
