探索Google Web Toolkit的实用功能与Drag&Drop解决方案

4星 · 超过85%的资源需积分: 3 28 浏览量更新于2024-07-28 收藏 10.8MB PDF 举报

《Google Web Toolkit解决方案：更多酷炫与实用》是一本专注于深入探讨Google Web Toolkit (GWT) 的专业书籍。该书由David Geary和Rob Gordon合著，旨在为读者提供一套全面且实用的GWT学习资料。GWT是一款强大的JavaScript框架，它允许开发人员在Java后端编写应用程序，并利用GWT编译器将其转换为可以在各种现代浏览器中运行的HTML/JavaScript代码。本书的核心内容之一是Solution1——Drag and Drop功能。GWT的Drag and Drop功能使开发者能够轻松地实现用户界面中的拖放交互，这对于构建现代Web应用的用户体验至关重要。通过学习这一章节，读者将掌握如何在GWT应用中实现元素的拖动、放置、排序以及数据绑定，提升应用程序的直观性和操作性。书中还涵盖了其他众多实用的GWT解决方案，包括但不限于： 1. **模块化和架构设计**：GWT支持模块化开发，有助于组织大型项目，使得代码结构清晰，易于维护。作者会介绍如何构建模块，管理依赖，并遵循良好的编程实践。 2. **性能优化**：GWT编译器可以生成高效的JavaScript代码，但开发者仍需了解如何通过优化UI渲染、减少DOM操作和缓存策略来提高应用程序的性能。 3. **跨平台兼容性**：GWT的应用程序能够在不同的浏览器上无缝运行，但处理浏览器差异和兼容性问题是必不可少的。书中会涉及这方面的解决方案和技巧。 4. **富客户端特性**：除了基础的Web交互，GWT还支持创建具有本地体验的应用，如使用Java的图形库和数据访问能力，提升用户的交互体验。 5. **部署和调试**：如何将GWT应用打包、部署到生产环境，以及使用调试工具进行故障排查，都是这本书的重要部分。 6. **社区和扩展**：GWT有着活跃的开发者社区，以及丰富的开源插件和扩展，作者可能会探讨如何利用这些资源加速开发过程。 7. **安全性和隐私保护**：随着Web应用的复杂性增加，如何处理敏感信息和保证安全性也是书中不容忽视的话题。《Google Web Toolkit解决方案：更多酷炫与实用》不仅是一本学习GWT的入门指南，也适合经验丰富的开发人员寻找提升技能和解决实际问题的参考资料。通过阅读本书，读者将能掌握GWT的强大功能，从而构建出更具竞争力的Web应用程序。

luxury of a hammer. GWT makes the most of existing tools. There are some good ham-

mers in software engineering, so it was a little bewildering to us why none could be

used effectively in Ajax development. We’re pretty adamant that the way to ensure

that web applications continue to improve is to leverage the good engineering tools

and practices that already exist. So rather than bemoaning the status quo, GWT allows

you to write your Ajax code in Java, leveraging concepts and patterns that have

become very familiar to UI developers; develop using proven development environ-

ments that include good code completion and refactoring tools like Eclipse; debug

your apps by running them in a real browser, using a solid debugger; then use a com-

piler to translate all that Java code to tiny, high-performance JavaScript that automati-

cally works around most browser quirks without so much as a nod from the develop-

er. And of course, make it possible to slip seamlessly into JavaScript when the need

arises to do things we never even anticipated. GWT is not about trends and language

wars, it’s about pragmatism and sound solutions.

This is why it pleases me greatly to see that David Geary’s GWT Solutions holds true

to its name and focuses on concrete and practical solutions. This is very much in keep-

ing with the spirit of GWT. It is not enough to talk about design patterns and elegance

of code without following through with why such things are relevant to your users.

David does a very nice job here of giving us something that goes beyond the contrived

example. Each of the solutions work well on two levels. First they take us through the

process of building good user interfaces in GWT making apparent the common pat-

terns and even calling attention to many of the likely pitfalls. But secondly, each of the

solutions is actually reusable in the form that he presents it. I will not be surprised to

see many of his examples showing up in future GWT applications. I think readers will

agree with the effectiveness of this approach. In fact, to hold the solutions to the same

crucial metric that I apply to GWT itself: Will Google Web Toolkit Solutions aid you in

creating applications that serve the needs of your users? I would have answer, Yes.

Kelly Norton, Google

Preface

There are what, six million Java developers? And the majority of those have used a

desktop application framework such as Swing. I speak about Google Web Toolkit

(GWT) regularly on the No Fluff Just Stuff (nofluffjuststuff.com) tour, at Java Users

Groups, and at other conferences, and one of the first things I do is ask how many of

the attendees have used either the Abstract Window Toolkit (AWT), Swing, or SWT.

The response is always about 95 percent.

What do AWT, Swing, and SWT have to do with Google Web Toolkit? In many

respects, GWT is Swing for web applications that do not require an enabling technolo-

gy like Web Start. GWT lets you develop applications that run in a browser using

familiar idioms from AWT, Swing, and SWT. After asking attendees if they’ve used

Swing, AWT, or SWT, the next thing I tell them is, “For those of you who raised your

hands, intuitively you already know how to use GWT.” Of course, they must learn a

new framework and API (and for that, they undoubtedly will need a good book), but

the point is that instinctively, they already know how to implement Ajax-enabled

applications that run in a browser. If you’ve used AWT, Swing, or SWT, and I tell you

that you typically write event handlers by implementing event handler interfaces in

anonymous inner classes with GWT, you know exactly what I mean. And if I tell you

that GWT provides adapter classes with no-op implementations of those interfaces so

you can selectively override only the methods that you are interested in, you should

feel like you’ve finally arrived home after a long and arduous journey coaxing simple

Ajax functionality out of JavaScript, HTML, CSS, and XMLHttpRequest objects. The

fact that GWT is so immediately accessible to so many developers is one of its greatest

selling points.

When Rob and I realized what GWT was and what it could do, we were very excited

about its potential. In fact, we were so excited that we decided to write this book. I’ve

written seven Java books over the past ten years, and it seems that no matter how

many books I write, it’s still a great deal of work to write another one, so I don’t com-

mit to a book unless I believe the topic has the potential to be the “next big thing.”

GWT was compelling enough for me to put my money on, and to spend six months of

my life to get this book in your hands.

But GWT is not just about building Ajax-enabled web applications. It’s about building

desktop-like applications that run in a browser. In this book, Rob and I show you how to

implement an application that lets you open multiple windows inside your browser,

where each window contains a map of an address you supply to the Yahoo! Maps web

service. You can drag the windows around inside the browser, resize the windows,

and drag the maps around inside their windows. Not only that, but you can zoom in

and out of the maps by manipulating a GWT widget that floats above the map inside

the window. You can also initiate animated scrolling, very similar to Apple’s animated

xvi Google Web Toolkit Solutions

Acknowledgments

Writing a book is never a solitary pursuit, and this book is no different. Many people

had a hand in taking this book from conception to bookstore shelves.

First, we would like to thank Kelly Norton from Google. Kelly is a Google engineer

who works on Google Web Toolkit (GWT), and his contribution to this book cannot be

understated. Kelly gave us excellent review comments and insights that only a GWT

engineer could have provided. He was instrumental in helping us modify our raw

code samples into refined examples that illustrate best practices and take advantage of

GWT nuances. In fact, many of the tips in this book are directly attributable to Kelly’s

comments.

We would also like to thank our other reviewers, who provided valuable feedback

ranging from comments on subject matter that gave us more thorough coverage to

coding suggestions that helped to increase the quality of the book’s code: Henry

Crutcher, Ido Green, Thad Humphries, Jeff Kurtz, Shailesh Mangal, Ted Neward, Sang

Shin, and Dick Wall. We also received great comments from Robert Kuhar and the

other folks at the WingDings Book Study Group.

We are also very grateful to Anthony Francavilla and Dan Moore. Anthony is CTO of

Colorado Homefinder, which maintains a real estate website (www.cohomefinder.com).

That website is a Struts application, implemented by Dan, with embedded GWT

widgets. Anthony and Dan were gracious enough to give us the code for their mort-

gage calculator, which we use in the last solution of this book on integrating the GWT

with legacy code.

Once again, Mary Lou Nohr was our technical editor, and as always, she not only pol-

ished our writing, but also taught us how to be better writers the next time around. It’s

because of Mary Lou that we now know things like: “Compound subjects modified by

‘each,’ ‘every,’ or ‘many a’ require a singular verb. When each follows a plural subject,

the verb is plural.” Thanks, Mary Lou.

Finally, we’d like to thank the folks at Prentice Hall who were instrumental in making

this book a reality. Greg Doench, our Signing Editor, orchestrated the many moving

pieces necessary to bring everything together; Christopher J. Zahn, Ph.D, our

Development Editor, who helped us with the book layout; and Kristy Hart, Senior

Project Editor, who took the book through production.

xviii Google Web Toolkit Solutions

剩余407页未读，继续阅读

shijielove

粉丝: 5
资源: 24

探索Google Web Toolkit的实用功能与Drag&Drop解决方案

ajax例子,Google Web Toolkit 1.0.21-ajax example, Google Web Toolkit 1.0.21

percona-toolkit-3.3.1-1-最新版.zip

Google Web Toolkit gwt-2.10.0 最新版本

toolkit documentation-x86_en-us.msi

conda search cudatoolkit --info

dpkg: 处理软件包 cuda-toolkit-10-2 (--install)时出错： 依赖关系问题 - 仍未被配置 在处理时有错误发生： cuda-toolkit-10-2

cudatoolkit11.3.1 duiying cudnn

dpkg: 处理软件包 cuda-toolkit-10-2 (--install)时出错： 依赖关系问题 - 仍未被配置 在处理时有错误发生： cuda-toolkit-10-2

percona-toolkit-3.0.12-1.el7.x86_64.rpm

最新资源

dpkg: 处理软件包 cuda-toolkit-10-2 (--install)时出错：依赖关系问题 - 仍未被配置在处理时有错误发生： cuda-toolkit-10-2

dpkg: 处理软件包 cuda-toolkit-10-2 (--install)时出错：依赖关系问题 - 仍未被配置在处理时有错误发生： cuda-toolkit-10-2