Warning: better arguments against setHandlerManager below:
My concern is that it is too easy to add handlers to a Widget and then set a new HandlerManager, expecting the old handlers to be transferred to the new HandlerManager. What would be the correct thing to do here? We can't transfer handlers because the HandlerRegistrations are linked to the old HandlerManager. Also, we've been trying to move to a model where we add Event Handlers in a widget's constructor instead of overriding onBrowserEvent(). Those handlers will be lost when we switch to a new HandlerManager, unless we unregister the old ones and register new ones. That complicates the widget creation process. If we require that the user specify the one and only HandlerManager when the first handler is added, then we avoid these problems. http://gwt-code-reviews.appspot.com/138801 -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
