Thanks, I didn't know about the Incubator widgets. It seems very complete and interesting but I have a question about it: What's the state of stability and feature completeness of the widgets in Incubator? I mean, are they ready to be used in real applications?
On Feb 4, 3:58 pm, Arthur Kalmenson <arthur.k...@gmail.com> wrote: > Hi getaceres, > > If you're looking for a sortable grid, check out the ScrollTable in > the gwt-incubator:http://code.google.com/p/google-web-toolkit-incubator/. If > you're > loading a lot of data into the ScrollTable, you might want to use the > BulkTableRenderer:http://code.google.com/docreader/#p=google-web-toolkit-incubator&s=go... > > -- > Arthur Kalmenson > > On Wed, Feb 4, 2009 at 4:51 AM, getaceres <getace...@gmail.com> wrote: > > > It's not only about the look, it's about the lack of a decent default > > widget set in GWT. > > We are starting a project now and in the very first phase we know that > > we need a sortable grid that could be very large, so what must we do? > > Must we implement a data model and a paging table or a big grid with > > caching or must we use one of Ext-GWT, IT Mill, or SmartGWT? Should I > > reinvent the wheel when there are three different toolkits with the > > widgets that I need? > > > On Feb 4, 9:57 am, "Miles T." <dupont.nico...@gmail.com> wrote: > >> Just a word about documentation. It is true that the documentation is > >> far from complete but it is not true that it is non-existent. > >> The wiki is in work in progress > >> :http://extjs.com/learn/Learn_About_the_Ext_GWT_Library > >> and there is also a small help centerhttp://extjs.com/helpcenter/index.jsp > > >> On 31 jan, 05:42, DaBlick <dabl...@gmail.com> wrote: > > >> > We used GWT-Ext and tossed it in favor of Ext-GWT (often referred to > >> > as GXT). > > >> > I've said this before in this forum so I'll just be brief here as you > >> > can search the forum for more details. > > >> > - It's been said MANY times so you know it's true: It wouldn't be > >> > accurate to say the documentation is poor. It'd be more accurate to > >> > say that the documentation is NON-EXISTENT and this is a SERIOUS > >> > SERIOUS issue you must consider before choosing it. You are, > >> > apparently, expected to learn the library by reverse-engineering the > >> > examples. This means your project will have a potentially steep ramp- > >> > up time. > > >> > - It's easy to find bugs in Ext-GWT because it's basically been a one- > >> > man project for most of its life. However... > > >> > - Reported bugs tend to get fixed VERY quickly and if you are > >> > licensed, you can pick up the fix from the SVN as soon as they are > >> > fixed. > > >> > - Ext-GWT has what I consider to be a rather nice MVC architecture > >> > built into it. It really goes well beyond, say, Swing's MVC because > >> > it not only de-couples Ms, Vcs and Cs, but decouples data-models, data > >> > "loaders", etc. The MVC architecture has some problems with its > >> > generic implementation, but it's pretty good overall. > > >> > - We think the components look nice, but then... we pretty much have > >> > customized everything. Our app is highly stylized. --~--~---------~--~----~------------~-------~--~----~ 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-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
