This link has been bookmarked by 67 people . It was first bookmarked on 28 Jun 2006, by Roan.
-
03 Jun 12
-
20 Mar 08
-
09 May 07
-
25 Apr 07
-
11 Jan 07
-
27 Oct 06
-
24 Oct 06
-
01 Sep 06
-
12 Aug 06
-
26 Jul 06
-
25 Jul 06
-
15 Jul 06
-
03 Jul 06
-
01 Jul 06
-
29 Jun 06
justin hardmanThe recently released Google Web Toolkit (GWT) is a comprehensive set of APIs and tools that lets you create dynamic Web applications almost entirely in Java code. Philip McCarthy returns to his popular Ajax for Java developers series to show you what ...
firefox:imported firefox:bookmarks ajax google java gwt programming
-
28 Jun 06
-
-
The recently released Google Web Toolkit (GWT) is a comprehensive set of APIs and tools that lets you create dynamic Web applications almost entirely in Javaâ„¢ code. Philip McCarthy returns to his popular Ajax for Java developers series to show you what GWT can do and help you decide whether it's right for you.
-
-
M Gfrom IBM developerworks, AJAX for Java developers
-
-
GWT also does a good job of abstracting away some of the low-level aspects of Ajax application development, such as cross-browser incompatibilities, the DOM event model, and making Ajax calls. But modern JavaScript toolkits such as the Yahoo! UI Library, Dojo, and MochiKit all provide a similar level of abstraction without needing to resort to code generation. Moreover, all of these toolkits are open source, so you can customize them to suit your needs or fix bugs that arise. This isn't possible with the black box of GWT (see the Licensing sidebar).
-
GWT does have a couple of fairly significant flaws. First among them is its lack of provision for graceful degradation. Best practice in modern Web application development is to create pages that work without JavaScript, and then use it where available to embellish and add extra behavior. In GWT, if JavaScript isn't available, you won't get any UI at all. For certain classes of Web application, this is an immediate deal-breaker. Internationalization is also a major problem for GWT. Because GWT client Java classes run in the browser, they have no access to properties or resource bundles to grab localized strings at run time. A complex workaround is available that requires a subclass of each client-side class to be created for each locale (see Resources), but GWT's engineers are working on a more viable solution.
-
The majority of Web applications fit quite comfortably into the page-centric model, and Ajax lets richer interaction paradigms be employed where needed. GWT does not play nicely with traditional page-centric applications. Although it's possible to combine GWT widgets with normal HTML form inputs, the state of a GWT widget is fenced off from the rest of the page.
-
-
05 Jan 89
Page Comments
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.