> I think you're getting hung up on the name, Stephen.
Yeah, I know. :-)
I'll get used to the name, I can just foresee explaining "no, this event
bus here in Widget isn't /the/ event bus" as a idiosyncrasy to fellow
team members/GWT newbies.
> HandlerManager was written before the notion of app
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
> 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 insi
In the case of HandlerManager, you just need to replace it with
EventBus/SimpleEventBus. The interface is nice if you're working with
gin and it's also nice for unit testing. If you don't want to be
bothered too much, just substitute all instances of HandlerManager
with SimpleEventBus and you're
I love how you deprecate core stuff, just like that. It shows how much
thought you put before introducing APIs. By now, it seems like half of
GWT API must be at deprecated state. No problem, simply slap
@Deprecated, @SuppressWarnings("deprecation") all over the place and
you 're done.
--
http://g
