That would work for this package, but other HTML5 stuff involves additions to core GWT classes, unlike the situation we had with cell widgets last time. It seems like it would be tough for stuff in gwt-user to have dependencies on bikeshed, and even tougher to avoid such dependencies while still coming up with a coherent architecture that doesn't make HTML5 feel like it's bolted on the side.
We can easily modify a build rule somewhere not to include com.google.gwt.experimental in a release build, if need be. Dan On Fri, Oct 29, 2010 at 2:11 PM, <[email protected]> wrote: > I'm not a fan of the experimental package being in GWT trunk. Can we > move this to trunk/bikeshed/ and just use the package name we expect it > to end up with "com/google/gwt/geolocation/"? That ensures that we > don't have to remove it if this isn't ready for GWT 2.1.1. It also > means we don't have to repackage everything when its ready for GWT > trunk, which was annoying the last time we moved stuff out of bikeshed. > > http://gwt-code-reviews.appspot.com/1060801/show > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
