I'll shoot from the hip and GUESS that the reason MIGHT be that (hopefully) someone is fixing what I currently think is a MAJOR flaw in the whole design/implementation of events in GWT.
If I'm correct (that there really IS a flaw), it's that there needs to be the concept of 'addEventListener' to every widget object (instead of forcing one to subclass each widget, as seems to be the case currently). The problem as I see it is that stuff like 'addClickListener' is very limiting, because you can't easily add events, like double-click, etc, etc. Sigh. [But, I could be all wet with my guess/hope.] On Dec 8, 11:06 am, Mike <[EMAIL PROTECTED]> wrote: > Hi all, > > Today i was browsing the latest source code for GWT and i saw that > many event-related classes have been deprecated. (E.g. CLickListener > and SourcesClickEvents.) Is a major refactoring of the event mechanism > forthcoming? > > (I was trying to figure out how the GWT event model works, i.e. i was > wondering what the rock-bottom source for GWT events is and how they > are `injected' into java. I discovered that GWT events are fired after > handling browser events. In my opinion, this is not clearly explained > in the GWT documentation. I worked an example, you can find it on my > blog whatmovesmike.blogspot.com .) > > Bye, Mike --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
