This week's book giveaway is in the OCP forum.
We're giving away four copies of OCP Java SE 8 Programmer II Exam Study Guide and have Kathy Sierra, Bert Bates, & Elizabeth Robson on-line!
See this thread for details.
Win a copy of OCP Java SE 8 Programmer II Exam Study Guide this week in the OCP forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

GWT's purpose and benefits  RSS feed

 
Ranch Hand
Posts: 329
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What is the purpose of GWT and how can one benefit from using it?

[Please use meaningfull titels so topics stand out and do not blend together. Important in Book promotions where you get 30-40 of the same title. Edited from GWT to GWT's purpose and benefits - Eric]
[ June 25, 2007: Message edited by: Eric Pascarello ]
 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's a Java-to-Javascript compiler: http://code.google.com/webtoolkit/overview.html
The main benefit is to code directly in Java (same IDE, type checking). It should be useful (I'm guessing) for complex client side logic

I think the main competitor is the Yahoo! UI Library ( http://developer.yahoo.com/yui ) that instead let you code directly in Javascript

I don't know what is the best way to code for AJAX purposes:
_ with a Java-to-Javascript compiler
_ plain an easy Javascript

In my past works I used the second way with Prototype


Filippo
[ June 25, 2007: Message edited by: Filippo Vitale ]
 
Ranch Hand
Posts: 74
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Filippo Vitale:

I think the main competitor is the Yahoo! UI Library ( http://developer.yahoo.com/yui )



Don't forget Dojo.


I don't know what is the best way to code for AJAX purposes:
_ with a Java-to-Javascript compiler
_ plain an easy Javascript


GWT is partly based on the premise that it is too messy to code in Javascript, so we simplify development by coding in Java instead.

Cheers,
Glenn

 
author
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ronnie,

For me the benefit of GWT will be reduction in through life costs of an application. With GWT:

1) Write program once; it takes care of browser differences for me
2) Program is writen in a strongly typed language with substantial tool support

Whilst the first point can be addressed by other toolkits/frameworks, GWT is the only one the readily allows us to use powerful IDEs, and other tools such as Ant and Maven.

Add these together with the ability to develop unit tests with JUnit, and all of a sudden the development environment of web applications becomes very similar to that for other solid development environments.

And where there is a solid development environment there is the opportunity for smarter, quicker (=cheaper) maintenance.

If we are serious about making web applications work, then through life costs will have to factor into the equation, and the more manageable my development the easier it is to make investement judgements etc and therefore theoretically the better/more functional my web applications could become.

Although this might perhaps sound a little "management" focussed, these issues are all valid as a developer, as anything that makes my life easier I find good for me!

This is not to say that you couldn't achieve something similar in just pure JavaScript, but you would be relying on "heros" in your team to deliver quality and reliability, and as applications get bigger these become harder to find / retain. There's a reason why we rarely write substantial applications in assembly code anymore.

//Adam
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!