As Sanjiv and Abhijeet mentioned, we still support GWT-Ext. However, we will not add new major functionality. We might still add some little things here and there and fix issues as they come.

We choose GWT-EXT 2 mounth ago and now you have to rewrite the whole application if we want to use a framework with major release, new big features and that will be style alive in a few years...

Ok, no problem, no one could know what will come tomorow.

But are you going to post somewhere a migration guide ??

For instance, all the showcase sample could be migrated to smartGWT in order to compare the different code.

What do you think about this ? We are about thousand guys using GWT EXT and we (our companies) need a guide to migrate to smartGWT.

Thank for your great job

I have worked with gwt-ext since the version 0.9.3. Migrating to 2.0 was really painful and the most difficult issues were the "small" problems mentioned in other posts here. We are developing a huge application with our customer which consists of several gwt modules at the moment and still grows. Moving to SmartClient means learn how to use the new API and change all modules. This will produce a lot of costs. A migration guide with the showcase moved to smartclient like mentioned by gattino would be very helpful.

I took a look at smartClient a while ago. It has a lot of nice widgets and features, but the rendering speed of the demo app is quite slow. While scrolling in the navigation tree or working with grids you can always see the rendering of images etc. (see attachment). Will there be perfomance enhancements in this section, because ext Js seems to be much faster.

You have done such a great job with gwt-ext that I'm convinced that you will be on the same high quality level with "smartclient-gwt".

Regards,


EDIT: I just found the showcase of SmartGWT and I'm impressed. Anyway the "slow rendering" problem only occurs in my firefox version (3.0.4). My collegue does not have this problem with the same browser and version.

gattino,
We are working on a migration guide. Many of the samples in the gwt-ext showcase are covered in the SmartGWT showcase but I agree that having a 1-1 version will help a lot of users. We'll look into it..

Sanjiv

mspecht,
A migration guide is in the works. We'll keep you posted.

Do you find the performance of SmartGWT demo http://www.smartclient.com/smartgwt/showcase/ to also be an issue? The SmartClient demo loads each sample in an IFrame I believe and the older "SmartClient" skin was also quite heavy which could explain the slowness.

Once the new blue / gray lighter skins are added to SmartGWT and ImageBundle's are used, things will appear / run a lot snappier. Both these are high priority.

Sanjiv

Hi sanjiv,

Thanks for the reply. My "performance issue" only occurs in my installation of firefox 3.0.4. My collegue with the same brwoser version does not have this problem. I read in one post that somebody had the same issue. It looks like the browser is always loading all images again while scrolling through the navigation tree (maybe no caching). In IE it looks okay and performance is no issue.

I spent some time to look at the SmartGWT showcase and API and I have to say that I'm impressed by its features. Using GWT-Ext and SmartGWT together would be perfect, so we would not have to migrate the code step by step.

That rings a bell. I've seen FF 3 mysteriously disable the cache when it crashes. Try entering about:config in FF3, and once you're in the settings, type "cache" on the search bar and make sure you have the following default settings



Try googling "FF cached disabled" and you'll see other threads like this http://forum.joomla.org/viewtopic.php?f=48&t=290924

Hope this helps..

Sanjiv

Hello.

Here at the company that I work we just started a big application using gwt-ext. I am not sure if we could migrate, there are issues (investigate the new framework, migration plans, see if it has all features from gwt-ext, etc.)
As said before a migration plan is needed. But I really think that a high priority are the gwt-ext themes. This is very very important and it should be considered seriously!
Equivalent themes should be developed, as the look & feel is very very important.

Thanks Sanjiv,

the configs were changed, "performance" issue solved

Will using two different package effect the number of concurrent connections requested?
http://msdn.microsoft.com/en-us/library/cc304129(VS.85).aspx
As stated here some browsers limit this number to 2. If it is still connecting to the same server will this only generate 1 connection since it is all GWT? I know using different ajax packages can cause multiple connections to be generated.

Thank you for your help.