Re: GWT event model
OK, but handler will use for Widget only or DOM element So ? On 15 déc, 15:07, "Arthur Kalmenson" wrote: > Listeners are now going to become Handlers. > > -- > Arthur Kalmenson > > On Mon, Dec 15, 2008 at 6:53 AM, step3...@yahoo.fr wrote: > > > So how can i set an eventlistener on a DOM Element in 1.6 ? is there > > new DOM methods to do that ? > > > On 15 déc, 03:43, "Arthur Kalmenson" wrote: > >> step3331, > > >> As Thomas said, those methods will be deprecated in 1.6 and removed in 2.0. > > >> -- > >> Arthur Kalmenson > > >> On Sun, Dec 14, 2008 at 7:44 AM, step3...@yahoo.fr > >> wrote: > > >> > Hello , > > >> > I use DOM.seteventlistener in my application. This method will be > >> > remove ? > > >> > Thanks > > >> > On 13 déc, 13:58, Mike wrote: > >> >> Great, thanks for the info! > > >> >> On Dec 12, 3:59 am, Sumit Chandel wrote: > > >> >> > Hi Mike, > > >> >> > As Adam mentioned, the new event system you discovered in trunk is > >> >> > indeed > >> >> > for GWT 1.6, following the design details explained in the link he > >> >> > posted > >> >> > above. > > >> >> > The new event system should solve some of the problems in the current > >> >> > Event > >> >> > system (as detailed in the doc), including the use case you mentioned > >> >> > in > >> >> > your first post. While the upcoming GWT 1.6 event system will be quite > >> >> > different from the current model in a breaking way, the change should > >> >> > lead > >> >> > to drastically improved performance and ease of development. > > >> >> > Hope that helps, > >> >> > -Sumit Chandel > > >> >> > On Mon, Dec 8, 2008 at 11:17 AM, Adam T wrote: > > >> >> > > It's for the version 1.6 event system: > > >> >> > >http://code.google.com/p/google-web-toolkit-incubator/wiki/ProposedEv... > > >> >> > > //Adam > > >> >> > > On 8 Dec, 17:06, Mike 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT event model
Listeners are now going to become Handlers. -- Arthur Kalmenson On Mon, Dec 15, 2008 at 6:53 AM, step3...@yahoo.fr wrote: > > So how can i set an eventlistener on a DOM Element in 1.6 ? is there > new DOM methods to do that ? > > On 15 déc, 03:43, "Arthur Kalmenson" wrote: >> step3331, >> >> As Thomas said, those methods will be deprecated in 1.6 and removed in 2.0. >> >> -- >> Arthur Kalmenson >> >> On Sun, Dec 14, 2008 at 7:44 AM, step3...@yahoo.fr wrote: >> >> > Hello , >> >> > I use DOM.seteventlistener in my application. This method will be >> > remove ? >> >> > Thanks >> >> > On 13 déc, 13:58, Mike wrote: >> >> Great, thanks for the info! >> >> >> On Dec 12, 3:59 am, Sumit Chandel wrote: >> >> >> > Hi Mike, >> >> >> > As Adam mentioned, the new event system you discovered in trunk is >> >> > indeed >> >> > for GWT 1.6, following the design details explained in the link he >> >> > posted >> >> > above. >> >> >> > The new event system should solve some of the problems in the current >> >> > Event >> >> > system (as detailed in the doc), including the use case you mentioned in >> >> > your first post. While the upcoming GWT 1.6 event system will be quite >> >> > different from the current model in a breaking way, the change should >> >> > lead >> >> > to drastically improved performance and ease of development. >> >> >> > Hope that helps, >> >> > -Sumit Chandel >> >> >> > On Mon, Dec 8, 2008 at 11:17 AM, Adam T wrote: >> >> >> > > It's for the version 1.6 event system: >> >> >> > >http://code.google.com/p/google-web-toolkit-incubator/wiki/ProposedEv... >> >> >> > > //Adam >> >> >> > > On 8 Dec, 17:06, Mike 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT event model
So how can i set an eventlistener on a DOM Element in 1.6 ? is there new DOM methods to do that ? On 15 déc, 03:43, "Arthur Kalmenson" wrote: > step3331, > > As Thomas said, those methods will be deprecated in 1.6 and removed in 2.0. > > -- > Arthur Kalmenson > > On Sun, Dec 14, 2008 at 7:44 AM, step3...@yahoo.fr wrote: > > > Hello , > > > I use DOM.seteventlistener in my application. This method will be > > remove ? > > > Thanks > > > On 13 déc, 13:58, Mike wrote: > >> Great, thanks for the info! > > >> On Dec 12, 3:59 am, Sumit Chandel wrote: > > >> > Hi Mike, > > >> > As Adam mentioned, the new event system you discovered in trunk is indeed > >> > for GWT 1.6, following the design details explained in the link he posted > >> > above. > > >> > The new event system should solve some of the problems in the current > >> > Event > >> > system (as detailed in the doc), including the use case you mentioned in > >> > your first post. While the upcoming GWT 1.6 event system will be quite > >> > different from the current model in a breaking way, the change should > >> > lead > >> > to drastically improved performance and ease of development. > > >> > Hope that helps, > >> > -Sumit Chandel > > >> > On Mon, Dec 8, 2008 at 11:17 AM, Adam T wrote: > > >> > > It's for the version 1.6 event system: > > >> > >http://code.google.com/p/google-web-toolkit-incubator/wiki/ProposedEv... > > >> > > //Adam > > >> > > On 8 Dec, 17:06, Mike 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT event model
step3331, As Thomas said, those methods will be deprecated in 1.6 and removed in 2.0. -- Arthur Kalmenson On Sun, Dec 14, 2008 at 7:44 AM, step3...@yahoo.fr wrote: > > Hello , > > I use DOM.seteventlistener in my application. This method will be > remove ? > > Thanks > > On 13 déc, 13:58, Mike wrote: >> Great, thanks for the info! >> >> On Dec 12, 3:59 am, Sumit Chandel wrote: >> >> > Hi Mike, >> >> > As Adam mentioned, the new event system you discovered in trunk is indeed >> > for GWT 1.6, following the design details explained in the link he posted >> > above. >> >> > The new event system should solve some of the problems in the current Event >> > system (as detailed in the doc), including the use case you mentioned in >> > your first post. While the upcoming GWT 1.6 event system will be quite >> > different from the current model in a breaking way, the change should lead >> > to drastically improved performance and ease of development. >> >> > Hope that helps, >> > -Sumit Chandel >> >> > On Mon, Dec 8, 2008 at 11:17 AM, Adam T wrote: >> >> > > It's for the version 1.6 event system: >> >> > >http://code.google.com/p/google-web-toolkit-incubator/wiki/ProposedEv... >> >> > > //Adam >> >> > > On 8 Dec, 17:06, Mike 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT event model
Hello , I use DOM.seteventlistener in my application. This method will be remove ? Thanks On 13 déc, 13:58, Mike wrote: > Great, thanks for the info! > > On Dec 12, 3:59 am, Sumit Chandel wrote: > > > Hi Mike, > > > As Adam mentioned, the new event system you discovered in trunk is indeed > > for GWT 1.6, following the design details explained in the link he posted > > above. > > > The new event system should solve some of the problems in the current Event > > system (as detailed in the doc), including the use case you mentioned in > > your first post. While the upcoming GWT 1.6 event system will be quite > > different from the current model in a breaking way, the change should lead > > to drastically improved performance and ease of development. > > > Hope that helps, > > -Sumit Chandel > > > On Mon, Dec 8, 2008 at 11:17 AM, Adam T wrote: > > > > It's for the version 1.6 event system: > > > >http://code.google.com/p/google-web-toolkit-incubator/wiki/ProposedEv... > > > > //Adam > > > > On 8 Dec, 17:06, Mike 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT event model
Great, thanks for the info! On Dec 12, 3:59 am, Sumit Chandel wrote: > Hi Mike, > > As Adam mentioned, the new event system you discovered in trunk is indeed > for GWT 1.6, following the design details explained in the link he posted > above. > > The new event system should solve some of the problems in the current Event > system (as detailed in the doc), including the use case you mentioned in > your first post. While the upcoming GWT 1.6 event system will be quite > different from the current model in a breaking way, the change should lead > to drastically improved performance and ease of development. > > Hope that helps, > -Sumit Chandel > > On Mon, Dec 8, 2008 at 11:17 AM, Adam T wrote: > > > It's for the version 1.6 event system: > > >http://code.google.com/p/google-web-toolkit-incubator/wiki/ProposedEv... > > > //Adam > > > On 8 Dec, 17:06, Mike 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT event model
Great, thanks for the info. -- Arthur Kalmenson On Fri, Dec 12, 2008 at 11:42 AM, Thomas Broyer wrote: > > > > On 12 déc, 16:18, "Arthur Kalmenson" wrote: >> Hi Sumit, >> >> Will you be removing the old event model or are you just deprecating >> it? i.e. if I upgrade to 1.6 when it comes out, will it break code >> that uses the old event model? > > Deprecate in 1.6, remove in 2.0. Upgrading to 1.6 shouldn't break > anything (other than generate deprecation warnings). > See also http://code.google.com/p/google-web-toolkit/issues/detail?id=3194 > > > > --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT event model
On 12 déc, 16:18, "Arthur Kalmenson" wrote: > Hi Sumit, > > Will you be removing the old event model or are you just deprecating > it? i.e. if I upgrade to 1.6 when it comes out, will it break code > that uses the old event model? Deprecate in 1.6, remove in 2.0. Upgrading to 1.6 shouldn't break anything (other than generate deprecation warnings). See also http://code.google.com/p/google-web-toolkit/issues/detail?id=3194 --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT event model
Hi Sumit, Will you be removing the old event model or are you just deprecating it? i.e. if I upgrade to 1.6 when it comes out, will it break code that uses the old event model? -- Arthur Kalmenson On Thu, Dec 11, 2008 at 9:59 PM, Sumit Chandel wrote: > Hi Mike, > > As Adam mentioned, the new event system you discovered in trunk is indeed > for GWT 1.6, following the design details explained in the link he posted > above. > > The new event system should solve some of the problems in the current Event > system (as detailed in the doc), including the use case you mentioned in > your first post. While the upcoming GWT 1.6 event system will be quite > different from the current model in a breaking way, the change should lead > to drastically improved performance and ease of development. > > Hope that helps, > -Sumit Chandel > > On Mon, Dec 8, 2008 at 11:17 AM, Adam T wrote: >> >> It's for the version 1.6 event system: >> >> http://code.google.com/p/google-web-toolkit-incubator/wiki/ProposedEventSystem >> >> //Adam >> >> On 8 Dec, 17:06, Mike 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT event model
Hi Mike, As Adam mentioned, the new event system you discovered in trunk is indeed for GWT 1.6, following the design details explained in the link he posted above. The new event system should solve some of the problems in the current Event system (as detailed in the doc), including the use case you mentioned in your first post. While the upcoming GWT 1.6 event system will be quite different from the current model in a breaking way, the change should lead to drastically improved performance and ease of development. Hope that helps, -Sumit Chandel On Mon, Dec 8, 2008 at 11:17 AM, Adam T wrote: > > It's for the version 1.6 event system: > > http://code.google.com/p/google-web-toolkit-incubator/wiki/ProposedEventSystem > > //Adam > > On 8 Dec, 17:06, Mike 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT event model
It's for the version 1.6 event system: http://code.google.com/p/google-web-toolkit-incubator/wiki/ProposedEventSystem //Adam On 8 Dec, 17:06, 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 -~--~~~~--~~--~--~---
Re: GWT event model
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 -~--~~~~--~~--~--~---
GWT event model
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 -~--~~~~--~~--~--~---
