IMO, it depends how "connected" and "coupled" you want your components. Having 3 display regions, you have very specialized and loosely coupled activities, and they have to communicate through events on the event bus. With a single display region, you have a more complex activity but its inner parts can "call" one another more directly.
The fact that you don't always have the center-north and center-south regions is not really relevant here (well, if your activities start asynchronously, you might experience some "flicker" when switching between two places that both need the regions, but that's another issue – disclaimer: we've not yet (re)introduced such "optional regions" in our app, so I have no concrete experience with this) -- 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.
