GWT Pragmatic book, informatyka, java
[ Pobierz całość w formacie PDF ]
Google Web Toolkit
Taking the pain out of Ajax
Ed Burnette
The Pragmatic Bookshelf
Raleigh, North Carolina Dallas, Texas
Prepared exclusively for Tomasz Pankowski
Many of the designations used by manufacturers and sellers to distin-
guish their products are claimed as trademarks. Where those designations
appear in this book, and The Pragmatic Programmers, LLC was aware of
a trademark claim, the designations have been printed in initial capital
letters or in all capitals. The Pragmatic Starter Kit, The Pragmatic Pro-
grammer, Pragmatic Programming, Pragmatic Bookshelf and the linking g
device are trademarks of The Pragmatic Programmers, LLC.
Useful Friday Links
•
from this book and
other resources.
•
•
To report
an erratum on a page, click the
link in the footer.
Every precaution was taken in the preparation of this book. However, the
publisher assumes no responsibility for errors or omissions, or for dam-
ages that may result from the use of information (including program list-
ings) contained herein.
To see what we’re up to, please visit us at
Copyright
©
2006 The Pragmatic Programmers LLC.
All rights reserved.
This PDF publication is intended for the personal use of the individual
whose name appears at the bottom of each page. This publication may not
be disseminated to others by any means without the prior consent of the
publisher. In particular, the publication must not be made available on the
Internet (via a web server, file sharing network, or any other means).
Produced in the United States of America.
+ $) -&!
Lovingly created by gerbil #52 on 2006-9-11
Prepared exclusively for Tomasz Pankowski
**',%"(#
1
. . . . . . . . . . . . . . . . . . . . . .
1
Contents
. . . . . . . . . . . . . . . . .
3
. . . . . . . . . . . . . . . . . . . . . .
3
5
. . . . . . . . . . . . . . . . . . .
5
. . . . . . . . . . . . . . . . . . . . . . . . .
5
. . . . . . . . . . . . . . . . . . . .
7
. . . . . . . . . . . . . . . . .
8
11
. . . . . . . . . . . . . . . . . . . . . . .
11
. . . . . . . . . . . . . . . . . . . . . . . . .
13
. . . . . . . . . . . . . . . . . . . . . . . .
15
. . . . . . . . . . . . . . . . . . . . . . . .
16
17
. . . . . . . . . . . . . . . . . . . . .
17
. . . . . . . . . . . . . . . . . . . . . . . .
19
. . . . . . . . . . . . . . . . . . . . . . . . . . .
20
. . . . . . . . . . . . . . . . . . . . . . . . . .
21
. . . . . . . . . . . . . . . . . . . . . . . . . . .
28
32
. . . . . . . . . . . . . . .
32
. . . . . . . . . . . . . . . . . . .
33
. . . . . . . . . . . . . . . . . . .
33
. . . . . . . . . . . . . . . . . . . . .
34
#"! %$
Prepared exclusively for Tomasz Pankowski
C
ONTENTS
CONTENTS
iv
. . . . . . . . . . . . . . . . . . . . . . . .
40
43
. . . . . . . . . . . . . . . . . . . .
43
. . . . . . . . . . . . . . . . . . . . . .
44
. . . . . . . . . . . . . . . . . . . . . . .
44
. . . . . . . . . . . . . . . . . . . . . . . . . .
45
48
. . . . . . . . . . . . . . .
48
. . . . . . . . . . . . . . . . . . . . . . .
49
. . . . . . . . . . . . . . . . .
49
. . . . . . . . . . . . . . . . .
50
. . . . . . . . . . . . . . . . . . . . . . . . . .
52
55
. . . . . . . . . . . . . . . . . . . . .
55
. . . . . . . . . . . . . . . . . . . . . .
58
. . . . . . . . . . . . . . . . . . .
59
. . . . . . . . . . . . . . . . . . .
61
#"! %$
Prepared exclusively for Tomasz Pankowski
Chapter 1
The Google Web Toolkit (GWT) was unveiled to an unsuspecting
public on May 18th, 2006 at the annual JavaOne conference in San
Francisco. The premise behind GWT is simple: make Ajax
1
develop-
ment easier by hiding browser incompatibilities from the program-
mer and allowing the developer to work in a familiar Java develop-
ment environment.
Introduction
The announcement was one of the highlights of the conference and
interest continues to grow. Developers have used GWT technology
in everything from games to mortgage calculators. The gwtPowered
lists over 100 examples, articles, widgets, and other
resources. Why has the Google Web Toolkit become such a hot
topic?
If you’ve ever written a non-trivial Ajax application before, then I’m
sure you can sympathize with the need to make the process easier.
If not, then a little background is in order.
1.1 Life before GWT
Dynamic web applications are typically written in several differ-
ent languages across two or more tiers. On the client side (the
part running in the browser), you have HTML markup of course,
1
The term Ajax was famously coined in February 2005 by Jesse James Garrett.
Originally it was an acronym for Asynchronous Javascript And Xml. The technol-
ogy has actually been around for a few years—for example it was used in Outlook
Web Access in 2000—but didn’t get much attention until Google popularized it
with applications such as GMail and Google Maps.
#"! %$
Prepared exclusively for Tomasz Pankowski
[ Pobierz całość w formacie PDF ]