Thank you John for your explanation. Now I understand the reason why you are shutting down the incubator. What I am suggesting is that developers should have a place where they can see what new features (libraries,...) are being developed and not to stumble upon this new features by chance (like I stumbled upon the doc for DataBackedWidgetsDesign for example). You mentioned that you send emails when you start a new project. What do I need to do to receive such an email? I think you guys at Google develop great libraries that are perhaps underused because they are hard to find. Let's take Gin for example (http://code.google.com/p/google-gin/). I think that more people would use it if you had a link to Gin from the GWT Tools and Libraries page.
Regards. On Jan 20, 5:29 pm, John LaBanca <[email protected]> wrote: > Libraries and widgets that we want to incubate will be moved into separate > projects. Instead of downloading one incubator jar, you'll be able to (have > to) download each project individually. Like Ray said, we're going to > commit most new features directly to trunk, but we may still want to > incubate some features if they are highly experimental. We often setup a > design doc and send out an email when we start a new project, such as the > data backed widgets, so the community can be involved. I'm sure we'll keep > doing that. > > The advantage of separate projects is that each project can move along at > its own pace. The incubator currently has some very stable features, some > highly experimental ones, and some deprecated code, and it isn't obvious > which is which (well, except the deprecated stuff). With individual > projects, it should be more obvious what the state of the project is. > > Thanks, > John LaBanca > [email protected] > > On Wed, Jan 20, 2010 at 10:57 AM, monkeyboy <[email protected]>wrote: > > > Then, how about a list of new features in the trunk since the last > > release. That way developers would know if they should become involved > > in the nontrivial (but not too hard) task of compiling GWT from > > source. I take the last comment back if such a list exists. I could > > not find it. > > > Regards. > > > On Jan 20, 4:26 pm, Ray Ryan <[email protected]> wrote: > > > On Wed, Jan 20, 2010 at 6:52 AM, monkeyboy <[email protected] > > >wrote: > > > > > Hello John. > > > > > I'm glad to see that PagingScrollTable will make it to the GWT trunk. > > > > Even now it is a useful widget but I can't wait to see the final > > > > version. I would like to ask a few questions. I am sorry to hear that > > > > the incubator will be shut down. I was wandering what (if anything) > > > > will replace it. With the incubator I as a developer had access to > > > > some tools and widgets that had a great chance to end up in the GWT > > > > trunk so I knew that they had a bigger chance to be supported and I > > > > dared to include them in my projects (eg. PagingScrollTable). I was > > > > burnt a few times with third party gwt libraries found on Google code > > > > for which the developer lost interest after a few months and I was > > > > left with a buggy library without support. > > > > > If the incubator is shut down how will we developers be able to find > > > > the new widgets and tools that are being "incubated" by Google > > > > developers? It is a bit hard to find them browsing trough Google code. > > > > I suggest that You put a couple of links in the Tools and Libraries > > > > section of gwt (http://code.google.com/webtoolkit/tools.html). It > > > > would be very helpful. > > > > Our intention is to be less bashful about developing things right in the > > > trunk. > > > > > Regards. > > > > > -- > > > >http://groups.google.com/group/Google-Web-Toolkit-Contributors > > > -- > >http://groups.google.com/group/Google-Web-Toolkit-Contributors > >
-- http://groups.google.com/group/Google-Web-Toolkit-Contributors
