i didn't read all post, but i ran into similar problems. now i got something that's working for me:
i decoupled activities/places and MVP (what thomas suggested in many places). in my case the VP-pairs are controlling/filling display areas and one activity is "start"ing/ controlling them. starting means composing the screen with a DockLayoutPanel and add the presenter's asWidgets to it's parts. controlling means hiding showing one shared content area for example. that is exactly the same what i did before without places/activities. the difference is now i can control/handle the leaving of such a set of presenters and i can easily safe some state (the presenters that want to save something need appropriate setters or constructors) / recover the state and bookmark it. imho that is the exact use for activities and places - to use an activity as presenter is imho a special case suitable in some (not so complex?) apps. what do you think about this approach? (this approach is my interpretation of answers i got for similar questions here https://groups.google.com/forum/#!topic/google-web-toolkit/0sM8aWWt27g, https://groups.google.com/forum/#!topic/google-web-toolkit/f20FbM04usU - in meantime i understand the - especially thomas' "Activities however are in no way related to MVP: you can use activities without doing MVP, and you can (and you probably will if your UI is complex) do MVP outside 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/-/aHihcB8jjncJ. 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.
