For example you could have a class that is responsible to show a message in your UI when it detects a long running task. Now this class needs the information when a tasks starts, when it stops and maybe it would also like to display a message depending on the task itself.
As these tasks could be started everywhere in your app you would use the EventBus to transport these information to your class that should show the message if the task takes too long. So you would have a TaskStartEvent(String taskMessage), TaskFinishedEvent() and you would fire these events in presenters/controllers and not inside widgets. Thats an example where you use the EventBus directly with custom events outside of widgets. And the map you have mentioned is not too complex. It has this structure because the EventBus supports handlers for specific event sources (which is the Object key in the map), see EventBus.fireFromSource() and EventBus.addHandlerToSource(). -- J. -- 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/-/NVVBWN94pzcJ. 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.
