I doubt there would be any elegant solution to this problem (which I
ran into as well). IMO it is the TypeH, H coupling inside
HandleManager that doesn't take into consideration the structure of
the handled event and rather matches one class (but not its
subclasses) to one EventHandler (while it
Soo sorry for cuttering your space but one correction to me previous
post:
That means, instead of having (in HandleManager)
public H extends EventHandler HandlerRegistration addHandler
(GwtEvent.TypeHtype, final H handler) {...}
have
public G extends GwtEventH, H extends EventHandler
2010/1/14 Ray Ryan rj...@google.com:
Piotr, even if the response to your work was muted the issue does come up a
lot. It would be great to see this in a project on code.google.com. Would it
make sense in that form?
I will see how hard it would be to ship it as a standalone project.
Afair the
Like Nathan mentions above, since last year's I/O presentation on
large GWT applications suggested the use of MVP and an event bus
(http://code.google.com/events/io/2009/sessions/
GoogleWebToolkitBestPractices.html), the entire GWT community seems to
have implicitly adopted HandlerManager as the
