Download Creating Dynamic Web Applications with Google Web Tools

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts
no text concepts found
Transcript
Creating Dynamic Web
Applications with
Google Web Tools
Prepared and Presented by: Brent Adkisson
For the Dynamic Languages User Group.
Why GWT?
 Because it is cool!
 Seriously, it gives the developer the ability to
write code and not worry about the issues of
cross browser development.
 Backed by a solid user group
http://googlewebtoolkit.blogspot.com
 100% Open Source
What is GWT?
 Google Web Toolkit (GWT)
GWT is Google’s open source AJAX
development kit.
 Makes development of browser applications
simple.
 Enables the same code to be used as a
desktop application.
 Java to Javascript compiler
The Basics
 GWT allows an architect to develop the
majority of the application in Java.
 Java code is translated into html objects
 Java code is also translated into Json
objects
Using the GWT
 GWT Uses Widgets for UI construction
 Similar to Swing Panels are used for widget
layout
 Buttons and other widgets use a click
handler
public class Hello implements EntryPoint {
public void onModuleLoad() {
Button b = new Button("Click me", new ClickListener() {
public void onClick(Widget sender) {
Window.alert("Hello, AJAX");
}
});
RootPanel.get().add(b);
}
}
Supports a Variety of widgets





Hierarchical trees
Tab Bars
Menu Bars
Modal Dialog boxes
List Boxes
Debugging and Deploying
 Hosted mode
 Web mode
GWT Architecture
How Well does it work?
 Compiler Generated Javascript size
A typical, full-featured GWT application will require the user to download
about 100K of cacheable JavaScript, which is in line with most hand-written
.
 End User Performance
AJAX applications
GWT applications are almost always as fast as hand-written JavaScript. The GWT
compiler avoids adding any wrappers around any functionality that is implemented
natively in the browser.
 Development Time
With so little time spent debugging problems in individual web browsers, you can spend
much more of your time on application functionality. Development time efficiency is our
favorite part of GWT.
Features




Dynamic reusable UI components
Simple to use RPC
Browser History Management
Real Debugging
Features





Browser compatible
JUnit Integration
Internationalization
Interoperability and fine grained control
Completely Open Source
References
Google Web Toolkit 1.3.3
(c) Copyright Google, Inc. 2006. All rights reserved.
Visit Google Code (http://code.google.com/webtoolkit/).
This product includes software developed by:
- The Apache Software Foundation (http://www.apache.org/).
- Tomcat (http://tomcat.apache.org/) with modifications
- Xerces (http://xerces.apache.org/)
- Tapestry (http://tapestry.apache.org/)
- The Eclipse Foundation (http://www.eclipse.org/).
- Java Development Tools (http://www.eclipse.org/jdt/)
- Standard Widget Toolkit (http://www.eclipse.org/swt/) with modifications
- The Mozilla Foundation (http://www.mozilla.org/).
- Mozilla 1.7.12 (http://www.mozilla.org/releases/mozilla1.7.12/)
- Rhino (http://www.mozilla.org/rhino/) with modifications
- The WebKit Open Source Project (http://www.webkit.org)
- The W3C consortium (http://www.w3.org/)
- The SAX project (http://www.saxproject.org/)