Good question. I haven't done a web app yet that uses activities/places, so I have only read a lot about it.
But if you have a token like #ListPersonDetailsPlace:1 to list details of a person with database id 1, an activity could load that person from the database and set it to the presenter it holds a reference to. That way an activity does the heavy work for restoring the application state defined by the HistoryToken and then configures the presenter and finally adds the presenters view to the display area. That way the presenter does not have to load anything to actually work and would only react to UI events and perform its logic (which could be already be lots of code) and the activity is responsible to configure the presenter and put it into the correct state. But maybe someone with more practically knowledge could give a better advise/example. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
