Файл: book-of-vaadin.pdf

Using Vaadin Add-ons

Then, just deploy the WAR to your application server.

Recompiling the Widget Set

The Vaadin plugin for Maven tries to avoid recompiling the widget set unless necessary, which sometimes means that it is not compiled even when it should. Running the clean goal usually helps, but causes a full recompilation. You can compile the widget set manually by running the vaadin:compile goal.

$ mvn vaadin:compile

Note that this does not update the project widget set by searching new widget sets from the class path. It must be updated if you add or remove add-ons, for example. You can do that by running the vaadin:update-widgetset goal in the project directory.

$ mvn vaadin:update-widgetset

...

[INFO] auto discovered modules [your.company.gwt.ProjectNameWidgetSet] [INFO] Updating widgetset your.company.gwt.ProjectNameWidgetSet

[ERROR] 27.10.2011 19:22:34 com.vaadin.terminal.gwt.widgetsetutils.ClassPathExplorer getAvailableWidgetSets

[ERROR] INFO: Widgetsets found from classpath:

...

Do not mind the "ERROR" labels, they are just an issue with the Vaadin Plugin for Maven.

After running the update, you need to run the vaadin:compile goal to actually compile the widget set.

17.4.3. Enabling Widget Set Compilation

If you are not using a POM created with the proper Vaadin archetype, you may need to enable widget set compilation manually. The simplest way to do that is to copy the definitions from a POM created with the archetype. Specifically, you need to copy the plugin definitions.You also need the Vaadin dependencies.

You need to create an empty widget set definition file, which the widget set compilation will populate with widget sets found from the class path. Create a src/main/java/com/example/AppWidgetSet.gwt.xml file (in the project package) with an empty <module> element as follows:

<module>

</module>

Enabling the Widget Set in the UI

If you have previously used the default widget set in the project, you need to enable the project widget set in the web.xml deployment descriptor. Edit the src/main/webapp/WEB-INF/web.xml file and add or modify the widgetset parameter for the servlet as follows.

<servlet>

...

<init-param>

<description>Widget Set to Use</description> <param-name>widgetset</param-name> <param-value>com.example.AppWidgetSet</param-value>

</init-param> </servlet>

Using Vaadin Add-ons

The parameter is the class name of the widget set, that is, without the .gwt.xml extension and with the Java dot notation for class names that include the package name.

17.5. Troubleshooting

If you experience problems with using add-ons, you can try the following:

•Check the .gwt.xml descriptor file under the the project root package. For example, if the project root package is com.example.myproject, the widget set definition file is typically at com/example/project/AppWidgetset.gwt.xml. The location is not fixed and it can be elsewhere, as long as references to it match. See Section 13.3, “Client-Side Module Descriptor” for details on the contents of the client-side module descriptor, which is used to define a widget set.

•Check the WEB-INF/web.xml deployment descriptor and see that the servlet for your UI has a widget set parameter, such as the following:

<init-param>

<description>UI widgetset</description> <param-name>widgetset</param-name> <param-value>com.example.project.AppWidgetSet</param-value>

</init-param>

Check that the widget set class corresponds with the .gwt.xml file in the source tree.

•See the VAADIN/widgetsets directory and check that the widget set appears there. You can remove it and recompile the widget set to see that the compilation works properly.

•Use the Net tab in Firebug to check that the widget set (and theme) is loaded properly.

•Use the ?debug parameter for the application to see if there is any version conflict between the widget set and the Vaadin library, or the themes. See Section 11.3.1, “Debug Mode” for details.

•Refresh and recompile the project. In Eclipse, select the project and press F5, stop the server, clean the server temporary directories, and restart it.

•Check the Error Log view in Eclipse (or in the IDE you use).

Chapter 18

Vaadin Calendar

The Vaadin Calendar is an add-on component for organizing and displaying calendar events. It can be used to view and manage events in monthly, weekly, and daily views.

Calendar will be included in Vaadin core framework in Vaadin 7.1.

18.1. Overview

The main features of the Vaadin Calendar include:

•Monthly, weekly, and daily views

•Two types of events: all-day events and events with a time range

•Add events directly, from a Container, or with an event provider

•Control the range of the visible dates

•Selecting and editing date or time range by dragging

Vaadin Calendar

•Drag and drop events to calendar

•Support for localization and timezones

The data source of the calendar can be practically anything, as its events are queried dynamically by the component. You can bind the calendar to a Vaadin container, or to any other data source by implementing an event provider.

Monthly and Weekly Views

The Vaadin Calendar has two types of views that are shown depending on the date range of the calendar. The weekly view displays a week by default. It can show anything between one to seven days a week, and is also used as a single-day view. The view mode is determined from the date range of the calendar, defined by a start and an end date. Calendar will be shown in a monthly view when the date range is over than one week (seven days) long. The date range is always calculated in an accuracy of one millisecond.

The monthly view, shown in Figure 18.1, “Monthly view with All-Day and Normal Events”, can easily be used to control all types of events, but it is best suited for events that last for one or more days. You can drag the events to move them. In the figure, you can see two longer events that are highlighted with a blue and green background color. Other markings are shorter day events that last less than a 24 hours. These events can not be moved by dragging in the monthly view.

In Figure 18.2, “Weekly View”, you can see four normal day events and also all-day events at the top of the time line grid.

Calendar Events

All occurrences in a calendar are represented as events. You have three ways to manage the calendar events: add them to the calendar and manage them by its API, from a Vaadin

Container, or with an event provider.

Events are handled though the CalendarEvent interface. The concrete class of the event depends on the specific CalendarEventProvider used in the calendar. By default, Calendar uses a BasicEventProvider to provide events, which uses BasicEvent instances.

Vaadin Calendar does not depend on any particular data source implementation. Events are queried by the Calendar from the provider that just has to implement the CalendarEventProvider interface. It is up to the event provider that Calendar gets the correct events.

You can bind any Vaadin Container to a calendar, in which case a ContainerEventProvider is used transparently. The container must be ordered by start date and time of the events. See Section 9.5, “Collecting Items in Containers” for basic information about containers.

A calendar event requires a start time and an end time.These are the only mandatory properties. In addition, an event can also be set as an all-day event by setting the all-day property of the event.You can also set the description of an event, which is displayed as a tooltip in the user interface.

If the all-day field of the event is true, then the event is always rendered as an all-day event. In the monthly view, this means that no start time is displayed in the user interface and the event has an colored background. In the weekly view, all-day events are displayed in the upper part of

Vaadin Calendar

Figure 18.1. Monthly view with All-Day and Normal Events

Figure 18.2. Weekly View

the screen, and rendered similarly to the monthly view. In addition, when the time range of an event is 24 hours or longer, it is rendered as an all-day event in the monthly view.

When the time range of an event is equal or less than 24 hours, with the accuracy of one millisecond, the event is considered as a normal day event. Normal event has a start and end times that may be on different days.