Removing the deprecated XxxListeners

[Thomas Broyer]

Hi Googlers,

I thought this was targeted to 2.0 but it didn't make it into it. What
I'm talking about is the complete removal of the event listeners,
which have been replaced by handlers since GWT 1.6.

I volunteer to provide the patch, but given that this is a bit of work
I'm asking here if I should start working on it, or if someone already
started the work, or if you'd rather have them stay for some
additional months (in this case, better spend time on more important
things).

Let me know ;-)

[Joel Webber]

A hearty +1 from me. We've been needing to do this for a while, but have been so heads-down on new features that it's fallen by the wayside. On that note, we also need to deprecate the DOM class and fix all the widgets to not use it (all its functionality was subsumed by Document/Element a long time ago). We're working on our 2010 roadmap right now, and this will definitely be a part of it.

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[Thomas Broyer]

On Mon, Jan 4, 2010 at 7:45 PM, Joel Webber <j...@google.com> wrote:
> A hearty +1 from me. We've been needing to do this for a while, but have
> been so heads-down on new features that it's fallen by the wayside. On that
> note, we also need to deprecate the DOM class and fix all the widgets to not
> use it (all its functionality was subsumed by Document/Element a long time
> ago). We're working on our 2010 roadmap right now, and this will definitely
> be a part of it.

That's Really. Good. News!

(thanks for this birthday gift ;-) )

--
Thomas Broyer
/tɔ.ma.bʁwa.je/

[Bruce Johnson]

Happy belated birthday!

> /tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/>
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>

[Olivier Modica]

Well, we've been pretty relieved to find out this didn't make it into
GWT 2.0 :) On a serious note we still have plenty of "old" code that
relies on that API and just like the GWT team we have to juggle
between new features and code maintenance, and certainly this would
have made our desired migration to 2.0 a much larger undertaking (and
less reliably estimated).

Obviously we support removing deprecated APIs and we've been writing
new code against the new API (and refactoring along the way), but
since this didn't make it into 2.0 please keep in mind the impact on
that change on existing deployments/products, I would hate for this
change to be slipped in a minor 2.0 maintenance release.

Thanks,
Olivier.