GXT 2.0-M1 upgrade experience

[dmallory]

I've seen various threads asking what to expect from a GXT 2.0 upgrade. For what it's worth, I'm currently working on a fairly complex enterprise application and we just took the plunge in hopes of resolving some lingering issues in 1.2.x. Our experience has been pretty lackluster so far, though not all that inconsistent with the GXT experience to date. However, this is obviously a preview version that we decided to take on early knowing the risks. On another note, core GWT 1.6 has felt quite positive. Details here for any interested:

http://lifeandcode.net/2009/04/gwt-1...de-experience/

[les]

Thanks for sharing your experience...

Any response from the GXT team?

[sven]

GXT 2 is a major release. Not a minor one from GWT 1.5 to GWT 1.6. It was never designed to work out of the box with 1.2 code.

So upgrading will brake existing code. Also note that M1 is an really early version. The version from SVN is arleady more stable than M1.


Most parts in GXT 2 are completly rewritten for greater performance.

[les]

Hi Sven,

Thanks for replying...

Can you reveal the release date for GXT 2.0?

[sven]

We are targeting June 15th for 2.0.

[Rvanlaak]

I see the Explorer is already using the GXT2 M2 release?

http://extjs.com/examples-dev/explorer.html

[jpnet]

dmallory:

Thank you for sharing your experiences with the community.

-JP

[dmallory]

In addition to the explorer using it, I noticed the release notes and build.properties changed to reflect M2 in svn this afternoon so I would guess the M2 timeframe is very soon...

[dmallory]

We've upgraded to M2 and it seems to be very similar to M1 but with noticeable quality and performance improvements. Definitely get M2 if you're on M1! Notes posted here.