There are several examples about gwt, such as :
http://code.google.com/p/gwtpetstore/
http://code.google.com/p/google-web-toolkit/source/checkout
http://code.google.com/p/gwt-google-apis/source/checkout
At last I managed to run gwt (Google Web Toolkit) with maven2. The tutorial is at the link below :
http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plugin/setup.html
Well, it's not entirely tutorial but from the official documentation. You could read that there are 2 way to use gwt, automatic or manual. Ebooks from all over the world usually taught the manual way with the combination with IDE plugin. I try to avoid all sort of IDE plugin because they make computer kind of slow with those plugins, and not to install any addition of engine if not really necessary. Apparently GWT provides them both, kind of cool development of javascript engine. Especially the automatic one.
Those are all technical, but the real reason why used GWT is to provide some kind of bridge between web development and native development. Maybe, in the near future, there would be no functional differences of applications between OS(Operating System), because applications are all build on top of web tier. That is possible with GWT as its engine. It's like one international language that everyone know, so no matter what machine its used, the machine could compile it and decide the application to be native or web based. As an analogy, you could make the application to be used for public (like newspaper) or you could translate it automatically to your own diary book (which is private).
Internationally used doesn't mean the easiest one.
Monday, April 20, 2009
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment