From GWT-EXT to SmartGWT

For the past three days I have been thinking of whether to shift to the new SmartGWT or stay with GWT-EXT. I told my self that not because Sanjiv(the original author of GWT-EXT) is out means I have to follow him to his new project.

To answer my own problem I decided to Google around my whole day to find a legitimate reason why I have to stay or move on. I finally decided to move on to SmartGWT and migrate most of my stuff on it pretty soon.

Here are the following solid reasons.

1. The GWT-EXT members are posting migration steps to SmartGWT and even recomend new developers who are starting Ajax to use SmartGWT. I think this is a solid justification.

2. Even though SmartGWT user interface sucks a little bit the team have assembled an elite members of designer to make the new and improve widgets more professional. Can't wait to see their new interface.

3. If I stay with GWT-EXT eventualy Google will upgrade their product and without the support of EXT-GWT things will be a mess. I don't consider using the native GWT since it lack's the richness that GWT-EXT and SmartGWT use. I can't hire developers to those stuff and it doesn't make sense to reinvent the wheel on my part.

That's it! Bye bye GWT-EXT. Hello SmartGWT.

Comments

mahi said…
Hi,
I read your blog. It is quite interesting. I am currently working on a project developed in gwt-ext. The project is under development for over 2 years and now we are considering a migration from gwt-ext to another framework like smartgwt or gxt. I have gone through some articles and still have not reached a conclusion. Since I have to change a huge amount of code base I am faced with some serious questions, which framework will be more good and which framework is easy for the migration? Hope you can provide me with a solution.

Thanx in advance
2:29 PM
maks said…
Hi Mahi,

If you choose the direction of smartgwt it provides a lot of instant features that will save you in your enterprise project but then again it won't scale up since it is just a wrapper. If you choose the direction of native GWT it is fast but it will take some time to rewrite most of your codes. For the GXT i don't have an experience with it so I can't really give you a comment.

Overall when you work on the web I think scalability is the most important. Your application must be fast since time is important to your users.

It's still up to you to decide.

Regards,
Mark
5:18 PM
Post a Comment

Popular posts from this blog

Apple's Edge Over Microsoft?

In the world of IT, models created by business empires will dictate the future of their products. Microsoft is using the component model as the key to win customers and Apple is using the end-to-end model. Microsoft Windows platform crushed Apple's Macintosh platform the day Microsoft release Windows 98 and pirates come out in the open and dominate every stall in our local mall and computer shops. iPod maybe the best and coolest mp3 player that I have ever seen but I still don't think that Apple will dominate the cell phone era for this place belongs to Asia particularly Nokia and Sony Ericson. I don't know why Walter Mossberg thinks US company will always dominate the world when in fact there is another company that belongs to the world and its called Open Source. I think he is dead wrong with his perception. Without a doubt nobody comes close to iPod in the field of mp3 player however, with the release of Sony Ericson latest cell phone such as W900i. An intelligent human ...
Read more

High Grounds Cafe - Best Internet Cafe in the Philippines

Image
I was looking for a nice place to chill last Monday to unwind my thoughts and enjoy with my family. I heard about the latest Internet Cafe just open 3 months ago and I decided to check it out. I have seen a lot of Internet Cafe but nothing comes close to this shop. Everything was simply high end from its ambiance, food and computers. It was simply the best place for people who want to collaborate and enjoy together.
Read more

GWT+MySQL Best Practice

Image
Migrating from GWT-EXT to native GWT has never been an easy task as I expect it would. I took me some moths to really absorb the fundamentals of its Java code, structure and pattern. The price for taking this challenge was undoubtedly more gratifying especially on performance and size. I had lesser reboot due to memory leak and I had better handling on syntax especially on database due to its strict use of its object. Here are some improvements on my code: DatabaseServiceImpl.java String url = "jdbc:mysql://localhost:3306/"; String db = "mydb"; String driver = "com.mysql.jdbc.Driver"; String user = "myuser"; String password = "mypassword"; public String connectDatabase() { String resultString; try{ Class.forName(driver).newInstance(); conn = DriverManager.getConnection(url+db, user, password); //conn = DriverManager.getConnection...
Read more