On Sun, Sep 1, 2013 at 6:16 AM, Jens <[email protected]> wrote:
> Something like an experimental policy would also be nice. I don't think it > makes that much sense to have half baked features in GWT. Prominent example > would be JSR 303 support which was included more than 2 years (IIRC) as > experimental. > I'm working on automatically refactoring all of Google's source code already, so I can easily update all of GWT's code as part of that. If you're interested in helping, probably the most useful thing to me would be if you could add more @Deprecated annotations throughout DOM (and Element and wherever else) along with appropriate @deprecated javadocs to explain what should be used instead. Once that's done, it shouldn't take me much work to cleanup all the call sites. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
