This week's book giveaway is in the Server-Side JavaScript and NodeJS forum.
We're giving away four copies of Micro Frontends in Action and have Michael Geers on-line!
See this thread for details.
Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

GWT in Action:Two questions

 
Ranch Hand
Posts: 434
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
1 Can it replace Java Applet totally? I'm now working on a Java Applet project, compare with AJAX, what are the advantages and disadvantages?

2 Will GWT be used by more and more people to build AJAX project? Or like GUI builder, although it can make GUI work easier, but there are still lots of people write code by hand.

Thanks.
 
Ranch Hand
Posts: 74
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Louis Wang:
1 Can it replace Java Applet totally? I'm now working on a Java Applet project, compare with AJAX, what are the advantages and disadvantages?



GWT output is Javascript, so it is limited by that language's capabilities. The end result is a web page. On the other hand, it will run in most all browsers without a JRE.

An applet is not a web page; it runs in a JRE. In particular a
signed applet can do many more client side tasks.


2 Will GWT be used by more and more people to build AJAX project? Or like GUI builder, although it can make GUI work easier, but there are still lots of people write code by hand.



If someone said they could predict the future, would you believe them?

Cheers,
Glenn
[ June 25, 2007: Message edited by: Glenn Murray ]
 
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As stated, you're limited by the language. GWT client side code only currently supports jdk 1.4 and even that is very limited in the JRE emulation. Check out this link that shows you the javadocs for the classes that are supported (http://code.google.com/webtoolkit/documentation/jre.html). Very limited indeed.

But with that said, I haven't had any problems writing a fairly decent size GWT application for our project. Pretty much if I can't do anything on the client side because of the limited emulation, I wrap the call in an RPC invocation and do it on the server side, which is full jdk 1.5 (or even 1.6) supported.
reply
    Bookmark Topic Watch Topic
  • New Topic