Is Ext-GWT still a nightmare?

Question

Just got back reading a question from 2 years ago here.

From there and several other places on the internet i concluded that developing with Ext-GWT was sucky.

My question is, with the release of GXT 3, whether it is still the condition now?

Answer 1

I have several GXT applications, one of which is ~35K lines. Have not found any of the problems other people mention.

I was doing straight ExtJs/JavaScript, then moved to GWT with the advent of GWT-EXT and later moved to Ext-GWT (GXT). I would still be doing ExtJs/JavaScript today if it were not for those two toolkits.

Performance issues: non issue on modern browsers. on IE6/7, you want to use common sense, displaying 1000 rows in a grid is not the best idea, from a performance and usability standpoint.

Answer 2

GXT is still crappy. We've been using it and although it provides some nice widgets it takes forever to write any business code. Most of our time is spent trying to get GXT to do the things we want. For example, using RPC is painfull because you have to keep converting from JPA entity beans to ModelData object (or some other object that can be serialized over RPC), Also there are inconsistances such as if you want to use the FormBinding object (which automatically maps between form elements and ModelData), then you can't use FieldSets which are really useful. FormBinding will only work with FormPanels and not FieldSets.

Also if you want to use the FileUploadField object you can't test it in Dev mode because of the post URL.

Basically, if you want to add 40% more time to your development fine. But otherwise go with a normal JavaScript framework.

Answer 3

We have been using GXT 2.x in the last one year while we built 3 projects with GXT.

Other than the lack of a WYSIWYG UI designer which makes the UI designing relatively slow compared to other frameworks, it is still IMO the best widgets library built on top of GWT.

So far we have not encountered any major issues with GXT.