Thursday, August 30, 2012

Re: Multiple modules (how to share outer container state and structure)

1.) Yes
2.) Never tried it but I would say yes as RootLayoutPanel is a singleton LayoutPanel and a LayoutPanel can have multiple childs. See LayoutPanel.add() JavaDoc.

Some general thoughts:
- one monolithic app gives you the best optimizations (code size, number of http requests while loading app/resources). But as your app grows DevMode will become slower and needs more RAM. To counter this, you should split your app into smaller GWT modules (without entrypoints), e.g. library.gwt.xml, community.gwt.xml, admin.gwt.xml, and then inherit them as library in App.gwt.xml. This allows you to use DevMode/SuperDevMode with your smaller GWT modules instead of the whole app. Some more information can be found here:

- When you want to use an outer shell application that loads "inner" GWT apps, each GWT app should have its own host page and the outer app shell should load them through an iframe. This gives you the ability to update each app independently but also provides some overhead as your clients need to download common code multiple times (e.g. GWT's own framework code, which is included in each app's JS). If you then need communication between your "inner" GWT app and the outer shell app, take a look at:

Personally I would go with the monolithic app that is split up into smaller pieces for easier development. Only if I would have a lot of different areas in my app and I want to update them independently I would consider an outer app + multiple independent "inner" apps approach.

Hope this helps.

-- J.

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

No comments:

Post a Comment