Hi,
FWIW, I wanted to mention that I'm glad HandlerManager got undeprecated.
I ran into a situation where a presenter already has the app's event bus,
and I also want to fire per-presenter events.
Without HandlerManager, I would have ended up with something like:
class Presenter {
EventBus appEventBus;
EventBus presenterEventBus;
}
And having two EventBuses in the same class just seems odd.
I prefer what I can do now:
class Presenter {
EventBus eventBus;
HandlerManager handlers;
}
Which keeps the clean notion that "the type EventBus == application-scoped
events" (which the EventBus javadocs even say is typically the case) and
"the type HandlerManager == instance-scoped events".
Even if the implementations are very much alike, I think there is value
in using the type system to differentiate the two use cases.
Perhaps this wasn't really worth mentioning, but I wanted to throw it
out in case HandlerManager is still in the running for deprecation.
Thanks,
Stephen
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
