Ouch! Total misunderstanding! First, a Place is akin to a URL, it represents the "current state" of your app. Given a Place instance, you should be able to determine which Activity goes into each "region" (btw, that's the role of ActivityMappers to return an Activity given a Place). You should have one ActivityManager *per* region you place Activities in; so you'll have 4 ActivityManagers, each one with its ActivityMapper, each one controlling a "display region". Given an "ExamPlace" for instance, the ActivityManager for the north region will ask its ActivityMapper which Activity (if any) to display (in the north region), the ActivityManager for the east region will ask its ActivityMapper which Activity to put in the east region, etc. And the PlaceHistoryManager will turn the Place into an history token thanks to its PlaceHistoryMapper; that's what you see in the URL; and if you go back to that URL (copy/paste, bookmark, back/next in the browser), the Place will be built back from the token, dispatched on the event bus, and each ActivityManager will then reconstruct the Activity for its "display region".
For a more in-depth look, see http://tbroyer.posterous.com, where I wrote a couple articles on Places, and couple others on Activities. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/2laIYIX71x0J. 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.
