[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

I've always been meaning to use it myself, so I just tried it and here's what appears to be the most useful thing you can do as an API or GWT developer: 1. Refactor your library using Eclipse 2. Review your history at any time with Refactor -> History 3. Package your refactorings - I did this via

[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

I haven't actually tried any of this stuff. I'll definitely have a look when I hunker down to do this refactoring. Of course, if anyone wants to look into it before I get to it, that would be even cooler... :) On Mon, Aug 3, 2009 at 12:13 PM, Fred Sauer wrote: > I wonder how much work we could m

[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

I wonder how much work we could make Eclipse do for us. Under the 'Refactor' menu there are a few useful optional to record / playback refactorings: Migrate JAR File Migrates a JAR File on the build path of a project in your workspace to a newer version, possibly using refactoring information stor

[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

I'd be a lot more comfortable if our own code didn't have reams of deprecation warnings. The good news is that it's actually pretty easy to do -- it's damned near rote, though not quite enough to automate. I did it for a few large classes in 1.5 (though I didn't commit the changes), just to make su

[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

On Mon, Aug 3, 2009 at 8:30 AM, Joel Webber wrote: > I've been wanting to do this since we first introduced the dom package in > 1.5. The plan is to remove all extant references to user.Element and > friends, as well as the DOM.* static methods, at which point they can be > deprecated. I'd like t

[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

Joel, I'll give your email to my project manager if you ever touch it again ;-) David On Mon, Aug 3, 2009 at 2:26 PM, Joel Webber wrote: > Sorry about that, David. I can promise with reasonable impunity that we > never, ever want to go through the process of changing the event system > again (

[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

Sam, I've been wanting to do this since we first introduced the dom package in 1.5. The plan is to remove all extant references to user.Element and friends, as well as the DOM.* static methods, at which point they can be deprecated. I'd like to do this as part of 2.0, so that we can go ahead and ge

[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

Sorry about that, David. I can promise with reasonable impunity that we never, ever want to go through the process of changing the event system again (FWIW, I had the dubious pleasure of updating about a bazillion lines of Google teams' code to deal with this change at one point). We never would ha

[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

Well, I don't like it that API's are changed that quickly - well I don't mind, it's my project manager that does not want us to spend time redoing existing things. But in our case most of the code is migrated to the new Event system, it was a lot of work since we have many apps using GWT. We sti

[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

Isaac, I would expect the maintainers of the various incubator 'ideas' to make an necessary updates. Similarly we expect the maintainers of other GWT related open source projects to make similar changes to their projects if they are in fact still using any deprecated APIs. Good ideas that have wor

[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

Yes, clean house :D On Aug 1, 11:22 am, Fred Sauer wrote: > To all GWT contributors- > > As you may know, there many exciting > things > we're working on for GWT 2.0. With all the new features coming > your way we thought GWT 2.0 wo

[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

Woo and, may I say, hoo, for removing deprecated code. Will deprecated code in the Incubator be disappearing as well? Obviously if that deprecated code depends on deprecated GWT code, it will at least have to be updated. On Fri, Jul 31, 2009 at 12:22 PM, Fred Sauer wrote: > To all GWT contribut

[gwt-contrib] Re: NOTICE - removing all @deprecated code for GWT 2.0

Nice! I love house cleaning. :-) Is there any plan for removing com.google.gwt.user.client.Element in GWT 2.0 or some time in the future? -Sam On Fri, Jul 31, 2009 at 12:22 PM, Fred Sauer wrote: > To all GWT contributors- > As you may know, there many exciting > things we're working on for GWT