Vaadin 6.4开发框架详解：构建企业级高质Web应用

需积分: 10 40 浏览量更新于2024-07-31 收藏 6.18MB PDF 举报

"《Book of Vaadin》是一本专著，详细介绍Vaadin 6.4版本的服务器端AJAX web应用开发框架。Vaadin是由Vaadin Ltd公司开发的，旨在帮助Java开发者构建高质量、易于使用的用户界面。该框架的核心特点是提供了一套现成的用户界面组件库，以及一个用于创建自定义组件的清晰架构。Vaadin强调易用性、可重用性、扩展性和对大型企业应用需求的满足，自2001年投入生产以来，已被证明是构建复杂商业应用的理想选择。书中内容涵盖了从基础入门到实际操作的全面指导。首先，介绍了Vaadin的基本概念，包括框架的概述、如何通过一个示例应用程序来体验其功能，并提到了与Eclipse IDE的集成支持。作者Marko Grönroos阐述了本书的目标和哲学，以及Vaadin的背景和技术优势。第二部分深入讲解如何开始使用Vaadin，包括安装步骤，如下载并安装官方发行包，启动内容浏览器查看内容结构，以及熟悉开发环境的配置。此外，还包括了演示应用程序的示例，以便读者能够快速上手实践。由于篇幅原因，部分内容未在摘要中详述，但可以预期后续章节将涵盖Vaadin组件的使用方法、布局管理、事件处理、服务器端编程、数据绑定、安全性、性能优化以及如何构建大型应用模块化等方面的知识。《Book of Vaadin》不仅适合初学者作为学习资源，也适合有一定经验的开发者查阅参考，以提升其Vaadin开发技能和项目管理能力。这是一本对于想要掌握Vaadin框架的开发者来说不可或缺的实用指南。"

Before going into details, we should note that this example source code is complete and does

not need any additional declaratively defined template files to be run. To run the program, you

can just add it to your web application, as explained in Section 4.8, “Setting Up the Application

Environment”.

1.3. Support for the Eclipse IDE

While Vaadin is not bound to any specific IDE, and you can in fact easily use it without any IDE

altogether, we provide special support for the Eclipse IDE, which has become the standard envir-

onment for Java development. The support includes:

• Import the installation package as a QuickStart demo project in Eclipse

• Install the Vaadin Plugin for Eclipse, which allows you to:

• Create new Vaadin projects

• Create custom themes

• Create custom client-side widgets and widget sets

• Edit components with a visual (WYSIWYG) editor

• Easily upgrade to a newer version of the Vaadin library

The Vaadin Plugin for Eclipse is our recommended way of installing Vaadin; the actual installation

package contains demos and documentation that are available also from the website, so you do

not normally need to download and install it, unless you want to experiment with the demos or

try debugging.

Installing and updating the plugin is covered in Section 2.2.5, “Vaadin Plugin for Eclipse” and the

creation of a new Vaadin project using the plugin in Section 2.4.1, “Creating the Project”. See

Section 8.4, “Creating a Theme in Eclipse”, Section 10.2, “Doing It the Simple Way in Eclipse”,

and Chapter 7, Visual User Interface Design with Eclipse (experimental) for instructions on using

the different features of the plugin.

1.4. Goals and Philosophy

Simply put, Vaadin's ambition is to be the best possible tool when it comes to creating web user

interfaces for business applications. It is easy to adopt, as it is designed to support both entry-

level and advanced programmers, as well as usability experts and graphical designers.

When designing Vaadin, we have followed the philosophy inscribed in the following rules.

Support for the Eclipse IDE4

Introduction

Right tool for the right purpose

Because our goals are high, the focus must be clear. This toolkit is designed for creating web

applications. It is not designed for creating websites or advertisements demos. For such purposes,

you might find (for instance) JSP/JSF or Flash more suitable.

Simplicity and maintainability

We have chosen to emphasize robustness, simplicity, and maintainability.This involves following

the well-established best practices in user interface frameworks and ensuring that our implement-

ation represents an ideal solution for its purpose without clutter or bloat.

XML is not designed for programming

The Web is inherently document-centered and very much bound to the declarative presentation

of user interfaces. The Vaadin framework frees the programmer from these limitations. It is far

more natural to create user interfaces by programming them than by defining them in declarative

templates, which are not flexible enough for complex and dynamic user interaction.

Tools should not limit your work

There should not be any limits on what you can do with the framework: if for some reason the

user interface components do not support what you need to achieve, it must be easy to add new

ones to your application. When you need to create new components, the role of the framework

is critical: it makes it easy to create re-usable components that are easy to maintain.

1.5. Background

The library was not written overnight. After working with web user interfaces since the beginning

of the Web, a group of developers got together in 2000 to form IT Mill. The team had a desire to

develop a new programming paradigm that would support the creation of real user interfaces for

real applications using a real programming language.

The library was originally called Millstone Library.The first version was used in a large production

application that IT Mill designed and implemented for an international pharmaceutical company.

IT Mill made the application already in the year 2001 and it is still in use. Since then, the company

has produced dozens of large business applications with the library and it has proven its ability

to solve hard problems easily.

The next generation of the library, IT Mill Toolkit Release 4, was released in 2006. It introduced

an entirely new AJAX-based presentation engine.This allowed the development of AJAX applic-

ations without the need to worry about communications between the client and the server.

Release 5 Into the Open

IT Mill Toolkit 5, released initially at the end of 2007, took a significant step further into AJAX.

The client-side rendering of the user interface was completely rewritten using GWT, the Google

Web Toolkit.

IT Mill Toolkit 5 introduced many significant improvements both in the server-side API and in the

functionality. Rewriting the Client-Side Engine with GWT allowed the use of Java both on the

client and the server-side. The transition from JavaScript to GWT made the development and

integration of custom components and customization of existing components much easier than

5Right tool for the right purpose

Introduction

before, and it also allows easy integration of existing GWT components. The adoption of GWT

on the client-side did not, by itself, cause any changes in the server-side API, because GWT is

a browser technology that is hidden well behind the API. Also themeing was completely revised

in IT Mill Toolkit 5.

The Release 5 was published under the Apache License 2, an unrestrictive open source license,

to create faster expansion of the user base and make the formation of a developer community

possible.

Stabilization of the release 5 took over a year of work from the development team. It introduced

a number of changes in the API, the client-side customization layer, and the themes. Many signi-

ficant changes were done during the beta phase, until the stable version 5.3.0 was released in

March 2009.

Birth of Vaadin Release 6

IT Mill Toolkit was renamed as Vaadin Framework, or Vaadin in short, in spring 2009. Later IT

Mill, the company, was renamed as Vaadin Ltd.Vaadin means an adult female semi-domesticated

mountain reindeer in Finnish.

The most notable enhancements in Vaadin 6 are the external development tools:

• Eclipse Plugin

• Visual user interface editor under Eclipse (experimental)

The Eclipse Plugin allows easy creation of Vaadin projects and custom client-side widgets. See

Section 2.2.5, “Vaadin Plugin for Eclipse” for details. The visual editor, described in Chapter 7,

Visual User Interface Design with Eclipse (experimental) makes prototyping easy and new users

of Vaadin should find it especially useful for introducing oneself to Vaadin. Like Vaadin itself, the

tools are open source.

While the API in Vaadin 6 is essentially backward-compatible with IT Mill Toolkit 5.4, the package

names and some name prefixes were changed to comply with the new product name:

• Package name com.itmill.toolkit was renamed as com.vaadin.

• The static resource directory ITMILL was changed to VAADIN.

• Client-side widget prefix was changed from "I" to "V".

• CSS style name prefix was changed from "i-" to "v-".

Other major enhancements in Vaadin 6 are listed in the Release Notes for Vaadin 6.0.0, which

also gives detailed instructions for upgrading from IT Mill Toolkit 5.

Birth of Vaadin Release 66

Introduction

2.1.1. Installing the Distribution Package

You can install the Vaadin installation package in a few simple steps:

1. Download the newest Vaadin installation package from the download page at http://vaad-

in.com/download/.

2. Unpack the installation package to a directory using a decompression program available

in your operating system (see below).

• In Windows, use the default ZIP decompression program to unpack the package into

your chosen directory e.g. C:\dev.

Warning

At least the Windows XP default decompression program and some

versions of WinRAR cannot unpack the installation package properly in

certain cases. Decompression can result in an error such as "The system

cannot find the file specified." This happens because the decompression

program is unable to handle long file paths where the total length exceeds

256 characters.This occurs, for example, if you try to unpack the package

under Desktop. You should unpack the package directly into C:\dev or

some other short path or use another decompression program.

• In Linux, Mac OS X, and other UNIX-like systems, use Info-ZIP or other ZIP software

with the unzip vaadin-6.x.x.zip command.

The files will be, by default, decompressed into a directory with the name

vaadin-6.x.x.

2.1.2. Starting the Content Browser

The Content Browser is your best friend when using Vaadin. It allows you to browse documentation

and example source code, and run the demo applications. The demo applications demonstrate

most of the core features of Vaadin.You can find the demo applications also at the vaadin website:

http://vaadin.com/demo.

To start the Content Browser, run the start script in the Vaadin installation directory as instructed

below.The start script launches a stand-alone web server running on the local host at port 8888,

and a web browser at address http://localhost:8888/.

The Content Browser will open the default web browser configured in your system. If your default

browser is not compatible with Vaadin the demo applications may not work properly. In that case

launch a supported browser manually and navigate to http://localhost:8888/.

If the Content Browser fails to start, make sure that no other service is using port 8888.

JRE must be installed

You must have Java Runtime Environment (JRE) installed or the batch file will fail

and close immediately. A JRE can be downloaded from ht-

tp://java.sun.com/javase/downloads/index.jsp.

Installing the Distribution Package8

Getting Started with Vaadin

剩余325页未读，继续阅读

ssyy556677

粉丝: 0
资源: 8

Vaadin 6.4开发框架详解：构建企业级高质Web应用

Vaadin7中文文档

Vaadin6.4.9中文开发手册

book-of-vaadin 8

Book of Vaadin - Vaadin 7 Edition

Book of Vaadin

book of vaadin

book of vaadin 7

Vaadin框架详解：Book of Vaadin 4th Edition

Vaadin7框架详解：Book of Vaadin 7入门实战指南

Leraning Vaadin

最新资源