Ed, I may be missing something from the original presentation, but your description of a limited number of Controllers interacting with your event bus seems identical in principle to a limited number of presenters interacting with the event bus (as in Ray Ryan's talk). Your limit on the number of controllers could be made as a similar limit on Presenters, and the concepts wouldn't really change (other than the location of where the event bus lives).
My take away on the event bus is that its still up to the programmer to exercise rigor in cleaning up references. With regard to the MVP design pattern and an event bus, there would seem to be a few ways to handle cleaning up Handlers on unload or navigation: your application could put all event bus handlers in the Presenter and use a Windows.ClosingHandler to place the Windows.Closing event on the event bus for all interested Presenters to handle, or you could supply an event between your Custom Widget/View to transfer the unload/detach event to the Presenter (note, this seems to follow the practice of passing events from View to Presenter as described in the talk. I do not claim to completely understand all aspects, but I like the concept of decoupling that actually seems a bit more logical, and the separation and testing capabilities afford by the MVP design pattern and Event Bus. V/r, Jason --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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 -~----------~----~----~----~------~----~------~--~---
