On 8 nov, 21:42, PhilBeaudoin <[email protected]> wrote: > Thanks Thomas. > > So the way I understand it, the ActivityManager/ActivityMapper are GWT > 2.1 equivalent's of GWTP's proxy for the purpose of navigation. It's > just that in GWTP you don't need to create or modify a separate class, > all is done within your presenter. > > In my apps, I often have some presenters that need to be awoken when a > given message transit on the bus. Say, for example, a ChatBoxPresenter > would like to wake up when a NewChatMessageEvent transits on the bus. > In GWTP it's simply a matter of annotating a method with @ProxyEvent > in the presenter -- ChatBoxPresenter is still lazily instantiated and > code split. How would you handle such a case in GWT 2.1 short of > instantiating the ChatBoxPresenter at app start?
As I understand it, your ChatBoxPresenter isn't related to a "place", i.e. it's "awoken" based on a "business event", not a navigation event; and in other words, it's not an Activity: case made. Activities (ActivityManager) is limited in scope to reacting to place changes and navigation (not that you couldn't use the Activity "contract" in other scenarios, such as your "chat box", but the ActivityManager wouldn't be the right tool for the job, you'd have to find/write another "activity manager" for your different use case). In other words: GWT 2.1 Activities won't replace GWTP as a whole (and I believe, as I already said in the past, that it's not its goal either). -- 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.
