On Tue, Jan 12, 2010 at 5:03 PM, Arthur Kalmenson <[email protected]>wrote:

> Hello John,
>
> This is really great news.
>
> >  We will build upon the lessons learned with these incubator widgets, but
> the API for the new data backed widgets will evolve significantly from the
> current APIs.
>
> Is this essentially data binding? Since you've put Form Validation at
> GWT 2.2, I guess you'd have to have data binding implemented before
> then?
>

We're still working on the requirements, but it will probably include some
form of data binding.  At the very least, it won't preclude data binding.


>
> > SliderBar and ProgressBar
> > Both of these widgets currently require the use of a global timer, which
> has
> > performance implications. If we can implement these without a resize
> timer,
> > we will include them in GWT 2.2. If we cannot, we will discontinue
> > development on them.
>
> If the performance issues are not sorted out, would it be possible to
> just spit it off into a different project instead of discontinuing it?
> Some people may be willing to accept a performance penalty to use
> these widgets.
>
> We might separate them into separate projects.  We'll have to figure out a
way to deprecate the incubator cleanly as people do currently depend on it
and may not switch to new widgets for a long time.  We'll probably leave the
incubator project around for quite a while after we stop working on it.


> > Graphics
> > The graphics library provides a single, platform independent API that
> works
> > on top of Canvas and VML. The library is not ready for GWT trunk, but
> this
> > project is worth pursuing.
>
> Will you be building on what was done in Speed Tracer for Canvas
> integration?
>
@Jaime - any thoughts on this?


>
> Thanks again for the update.
>
> All the best,
> --
> Arthur Kalmenson
>
>
>
> On Tue, Jan 12, 2010 at 1:04 PM, John LaBanca <[email protected]> wrote:
> > Incubator Users -
> >
> > The Google Web Toolkit Incubator project began as a proving grounds for
> new
> > widgets to be vetted before joining the ranks of the GWT trunk. We've
> seen
> > some success stories over the last year with EventHandlers, ClientBundle,
> > and DatePicker, but for many of the widgets and libraries, Incubator has
> > become an elephant graveyard.
> >
> > In order to address this issue, we will start graduating some of the
> > libraries to GWT trunk, move some into separate projects, and discontinue
> > development on others. Ultimately, we will wind down the incubator
> project
> > completely.
> >
> > The schedule below shows the fate of each subproject in incubator. It's a
> > tentative schedule, meaning that it could change as priorities shift.
> >
> > GWT 2.1
> >
> > PagingScrollTable and FastTree
> > We are working on a new set of data backed widgets for GWT 2.1 that will
> > include APIs for trees and tables. We will build upon the lessons learned
> > with these incubator widgets, but the API for the new data backed widgets
> > will evolve significantly from the current APIs. When the data backed
> > widgets are added to GWT trunk, we will stop development on
> > the PagingScrollTable and FastTree.
> >
> > Locale Selection
> > Selecting the locale on the server requires one less round trip to the
> > server on startup and is needed for effective use of
> > runtime locales selection.  This library will be included in GWT 2.1.
> >
> > GWT 2.2
> >
> > CollapsiblePanel
> > This widget will probably become a subclass of DockingLayoutPanel,
> similar
> > to SplitLayoutPanel.
> >
> > SliderBar and ProgressBar
> > Both of these widgets currently require the use of a global timer, which
> has
> > performance implications. If we can implement these without a resize
> timer,
> > we will include them in GWT 2.2. If we cannot, we will discontinue
> > development on them.
> >
> > Logging
> > The logging API may make it into GWT 2.1 if time permits.
> >
> > Form Validation
> > We will take a closer look at the form validation API in GWT 2.2..
> >
> > Separate Project:
> >
> > SoundResource
> > SoundResource is a promising API for including sound in an application,
> but
> > it makes sense to wait for HTML 5 features to become widely adopted
> before
> > including it. We would like to move SoundResource into the gwt-voices
> > project: http://code.google.com/p/gwt-voices/.
> >
> > Graphics
> > The graphics library provides a single, platform independent API that
> works
> > on top of Canvas and VML. The library is not ready for GWT trunk, but
> this
> > project is worth pursuing.
> >
> > HtmlDecorators
> > We will continue to work on this project to arbitrarily add decorations
> to
> > widgets.
> >
> > As always, please feel free to reply with comments or suggestions.
> > Thanks,
> > John LaBanca
> > on behalf of the GWT team
> > --
> > 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

Reply via email to