I use an object called ApplicationModel, that is passed to every presenter on creation. It stores application state, as its name might suggest. It also fires off events whenever any of the presenters modifies one of its values, which helps keep the application in sync. Things like user roles and what the user has currently selected are stored in there.
I should also mention that the ApplicationModel is actually handed off to the presenter as part of an ApplicationBundle, which is basically just a parameter object. It holds the model, the ApplicationNavigationControl, ApplicationEventBus, ApplicationFactory, etc. Wrapping it all up in the parameter object makes it really easy to add new application-wide bits. -Ben -- 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/-/51lt6kbjjoQJ. 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.
