Re: EventBus and HandlerManager Classes. Difference?

Thanks very much, Thomas. This make a little more sense. I keep
looking at the base roo application and it is showing ( I think as of
M3 with the ScaffoldFactory) the use of the HandlerManager.

So it is good to hear that for certain that we are moving away from
HandlerManager and to implementations of the EventBus.

Thanks very much!

On Sep 17, 4:12 pm, Thomas Broyer <t.bro...@gmail.com> wrote:
> On Sep 17, 9:05 pm, Ashton Thomas <ash...@acrinta.com> wrote:
>
> > I am confused as to when use the abstract class EventBus class that
> > implements HasHandlers:http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/...
>
> > and the class HandlerManager that also implements HasHandlers:http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/...
>
> > I know we have th SimpleEventBus that extends EventBus but I am still
> > a bit confused. Can anyone do a brain dumb or drop some info?
>
> Basically, HandlerManager is only to be used within widgets (and it is
> an internal part of Widget, backing the addHandler and addDomHandler
> methods; so you shouldn't have to use it directly, probably the reason
> it's marked @Deprecated).
>
> If you need an event bus to make you apps components communicate with
> each others, then you should use EventBus, which SimpleEventBus is an
> implementation.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.