How about using a single NativePreviewHandler into which "screens" (or other widgets) will "register"? Or how about having thins NativePreviewHandler singleton fire events on the EventBus, and have "screens" and other widgets add handlers to the EventBus?
(BTW, Activities make it easy to manage the lifecycle of your "screen parts", which makes it easy to register/unregister things –it's even easier with the EventBus, as you don't even have to explicitly remove your handlers–) -- 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/-/udDSY8Xb7BwJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
