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
GWT 2.2
Separate Project:
Can we still expect to see a 2.0-compatible version of the current gwt-
incubator.jar?
On Jan 12, 10:05 am, John LaBanca <jlaba...@google.com> 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*
On Jan 12, 1:05 pm, John LaBanca <jlaba...@google.com> 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.
Will the TableModel classes and the CellRenderer classes make it into
the GWT trunk? If the table widgets go across, will they be redone to
work
with GWTEvents instead of AbstractEvent? Can I work with only one type
of
HandlerManager?
Respectfully,
Eric Jablow
Cheers
Gabriel
On Jan 12, 6:05 pm, John LaBanca <jlaba...@google.com> 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*
On Jan 12, 4:19 pm, Gabriel Guerrero <gabrieldavidguerr...@gmail.com>
wrote:
Is there a way we can get visibility into everything the GWTers are
planning for each release (i.e. the roadmap)? If you guys take the
position that you don't want to set expectations that won't be met...
can you send me a copy personally? I promise not to build up my
expectations :)
On Jan 12, 11:05 am, John LaBanca <jlaba...@google.com> 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*
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Regarding the logging API, the gwt-log project is also worth
considering: http://code.google.com/p/gwt-log/
Of course, if I had an existing application based on some of the
incubator's widgets (such as one of the two PagingScrollTables), I
might fear the API changes... A migration path would be a good idea in
such a case :) (as well as a release of the gwt-incubator compatible
with GWT 2.0, for those using the existing widgets).
Keep up the good work, GWT is awesome.
- Etienne
On Jan 12, 7:05 pm, John LaBanca <jlaba...@google.com> 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*