On Feb 4, 3:57 am, "Miles T." <[email protected]> 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.
Well, it's not "true" that I said it was non-existent either. :-)
I said it was more accurate to say it was non-existent than it was to
say that it's poor.
I looked at the recent additions to the Wiki that you pointed me to,
and I still maintain the accuracy of my characterization but...
1) We ARE using Ext-GWT and we are glad we are using it.
Documentation is a serious complaint but we're happy
otherwise. It's just our biggest beef and people considering
using GXT need to be aware of it, which was my point.
2) ExtJS is VERY responsive to bugs and questions, and the forums are
very helpful. Not a substitute for
documentation, but they dull the pain considerably.
3) I'm ecstatically happy to see that a book is coming out. I'm
going to preorder copies for all my colleagues. This
could eliminate the entire complaint if the book is decent.
4) I'm quite happy that work is being done on the Wiki. But the fact
remains, that not much is there yet. As far as
I can tell, the GXT MVC architecture (which IMHO is pretty darn
good) is largely undocumented. One sentence
descriptions often in the Javadocs even.
> 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 <[email protected]> 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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
