View Full Version : API consistency of GXT 3.0 and 3.1

5 May 2014, 11:38 PM

we are wondering if the GXT 3.0 API is consistent with the upcoming GXT 3.1 - we are going to upgrade our web app, currently written in GXT 2.3, to GXT 3.x. are there many breaking changes in API in GXT 3.1 in comparsion with GXT 3.0? because, if that is the case, we will delay our upgrade until final version of GXT 3.1 is out, so we won't need to rewrite the code base (based on GXT 3.0) again when GXT 3.1 is out.

thanks a lot!

Colin Alworth
6 May 2014, 7:48 AM
There are some API breaking changes, but they are pretty minimal - I'd encourage you to check the release notes file in the download zip, which goes over every single api change from 3.0.

The change from 3.0 to 3.1 is nothing like 2.3 to 3.0. When we released GXT 3.0 about two years ago, we had to catch up with a number of changes in GWT, which required changing how GXT behaves in many cases. Keep in mind though, that GXT 2 and 3 can be run together in the same project for an easier migration process.

6 May 2014, 9:20 AM
Do you have GXT2.3.1 patch that can work together with GXT3.1.0 and GWT2.6?

Colin Alworth
7 May 2014, 11:34 AM
As soon as we kick 3.1.0 out the door, we'll start focusing on that. We've had some very positive responses from a few support customers who have tried it (if you'd like a pre-release copy, open a support ticket and we'll hook you up), but while our QA efforts have been focused on GXT 3.1, we haven't had time to verify the stability of GXT 2.3 with GWT 2.6.