EventBus is a really nice mechanism to *decouple methods from callbacks* by adding corresponding event handlers to an EventBus.
By nature EventBus is something that should be known to both classes, the calling and the called class. So you can *1. pass an EventBus in a constructor or* *2. use a static EventBus that can be called from any View* Is there a rule of thumb how you should use an EventBus? So far I saw only constructor usage examples. Are there some significant disadvantages that come with a static EventBus? -- 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/-/1W_HXJS76-AJ. 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.
