Another option is to use a framework that you know is going to stick around through each iteration, such as GXT or Vaadin, which are both part of the steering committee and would be the likely candidates for continuing a widget hierarchy.
I am personally hoping we will see the base Widget classes remain in GWT proper and the rest of the actual widgets broken into several parts, UIBinder, CellWidgets, and possibly LayoutWidgets as separate libraries, then you only import what you need and someone can pick up the maintenance of each or add additional libraries like GWT-Polymer or something that are still compatible between them. That would be the biggest loss to remove Widget from GWT proper, possible loss of compatibility between different widget sets without jumping through a bunch of hoops. On Friday, December 11, 2015 at 10:36:39 AM UTC-7, [email protected] wrote: > > As I understand the new advise for using GWT is when we need ready > components such as lists, grids etc. we are encouraged to use ui components > from polymer or other such framework. > > Is this understanding correct ? > > If yes, why so ? > > If not, is it a good idea to create a new pure GWT Ui component library on > the lines of smart GWT / ext-gwt ? > > TIA, > Gautam > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
