You're correct. The GWT Steering Committee has said that the next major version of GWT (3.0) might get rid of the Widget library. I personally think that it will continue to exist even if it's not GWT proper (as a separate library/module), simply because for some it's a better/faster way to create UI elements. Another option is to use neither Widgets nor external libraries, but create your own "widgets" by using html/css (UiBinder) and gwtquery for instance to attach event handlers as mentioned in this presentation:
http://www.slideshare.net/Arcbees/best-development-practices-for-gwt-web-applications This is the approach I'm using more and more. On Monday, December 14, 2015 at 6:08:36 AM UTC-7, [email protected] wrote: > > Hi everybody, > > I feel a bit sorry/sad that no one found this post interesting enough to > comment :( .. > > trying my best to get some ideas. Please help. > > thanks, > Gautam > > On Friday, December 11, 2015 at 7:36:39 PM UTC+2, [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.
