I think you're getting hung up on the name, Stephen. The only differences between the two classes is that the move to EventBus gave us a chance to simplify the api. They do they same thing, and for the most part an EventBus is a drop in replacement for a HandlerManager.
HandlerManager was written before the notion of app wide events had taken hold, and would have been a simpler beast had that been true. As a team and a community, we backed into using HM for that purpose. Re: our habit of not cleaning up after our deprecations, guilty as charged. I'm hoping we can get on top of that soon. On Mon, Oct 18, 2010 at 10:17 AM, Stephen Haberman < [email protected]> wrote: > > > If you don't want to be bothered too much, just substitute all > > instances of HandlerManager with SimpleEventBus and you're done. > > I dunno--per my comment in a proposed patch to SimpleEventBus, I find > using "EventBus" in all the places I used HandlerManager to be odd. > > I used HandlerManager inside of objects to handle object-specific events > (much like it's used in Widget for Widget-specific events). To me, this > usage isn't an event bus...event bus == app-wide stuff. > > Having an "app-wide" EventBus field inside of a Widget (or Property or > whatever) leads to confusion: this is /the/ app-wide event bus, or > just /a/ object-specific event bus. > > IMO, keeping the two classes separate makes more sense to me. The > satisfy two separate roles in an app. That their internals are fairly > similar is an implementation detail. > > (re: dmen, I enjoyed your message. :-) > > - Stephen > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
