In a few words: use EventBus to communicate between "big parts" of your app (e.g. between activities, if you use Places&Activities); you don't need an EventBus when dealing with widget events, simply use the widget's built-in mechanism: addHandler/addDomHandler, fireEvent. Use EventBus for higher-level (generally business-related) events: got there, done that, etc. e.g. "we'll be going to the User #123, U OK?" (PlaceChangeRequestEvent), "we've arrived at User #123" (PlaceChangeEvent), "Saving User #123" (custom event of your own), "User #123 has changed" (EntityProxyChange), "oops, looks like we've been signed out, session expired?" (custom event of your own).
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/eKeKnGUZPXwJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
