About GWT 2.0 and Swing 2.0

I have read today GWT's Future: 2.0 and My Wishes and then, I have suggested to develop a GWT implementation on top of Java2D or Swing. Then, GWT developers would have the choice of the target platform: browsers or rich Java clients.

I mentioned Java2D because I know Pivot aims to build rich internet applications in Java on top of Java2D, that is, trying to propose a Swing 2.0 approach (see this interesting page listing Pivot advantages through this perspective). While GWT is popular, leveraging GWT to do rich Java client programming following a Swing 2.0 perspective could be a good way to promote such a perspective.

There are different projects enabling to propose both kind of deployments, a rich Java client deployment and a web-oriented deployment. Some projects enable, for example, to deploy Swing applications in browsers, that is, to give a web-based interface to Swing applications. I could mention AjaxSwing, Swingweb, Wings.

Having the choice of the target platform is interesting for different reasons. Let's mention the following ones:
- it would enable to share the same tools for developing rich Java clients, and for developing web-based applications.
- it would provide different targets for different audience (a web-oriented deployment for occasional users, and a rich Java client for regular users) from quite the same code.

Posted at 12:09AM Jun 30, 2009 by Dominique De Vito in Developer  |  Comments[0]