Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I have worked pretty heavily with both flavors of the GWT Ext libraries, though I've spent more time with GXT recently.</p> <p>My first general response would be a question back to you, are you building something for deployment to the world at large, or is this to be something for an intranet application? </p> <p>Onto some pros and cons</p> <p><b>Pros</b> <li>Lots of nifty widgets, some are very powerful <li>Pretty slick default styling, certainly good enough for lots of internal uses <li>Demo application source is pretty good for getting something going quickly. This is balanced by the con on documentation though...</p> <p><b>Cons</b> <li>Customizing -> Pain, lots and lots of pain <li>'MVC' that ships with the thing is not very good and probably should not be used if you value your sanity. (<a href="http://blog.gerardin.info/archives/40" rel="nofollow noreferrer">http://blog.gerardin.info/archives/40</a>) <li>Documentation is pretty lacking, some of the widgets have some rather sophisticated things happening behind the scenes and this is all undocumented.</p> <p>To put this into context, we are currently migrating away from GXT as we've found that we're now spending more time working around the library and fixing it's defects than we are saving time by using the library. </p> <p>In general, if the widgets look useful to you and the functionality that you see in the GXT demo is EXACTLY what you need, then GXT is a pretty good library to go with. If you want to use the widgets in any mildly unsanctioned way or extend them, I would strongly suggest staying away from the library as you are only setting yourself up for some painful migration in the future.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload