1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Vaadin @version@</title>
<link rel="stylesheet" type="text/css" href="demo/css/styles.css" />
<!--[if lte IE 6]>
<link rel="stylesheet" type="text/css" href="demo/css/ie.css" />
<![endif]-->
</head> <!-- /head -->
<body>
<div id="header">
<h1>Vaadin – thinking of U and I</h1>
<div id="version">
<strong>Version @version@</strong>
<a href="javascript:history.go(-1);" title="Back to index page">« Back</a>
</div>
</div> <!-- /header -->
<div id="content">
<p>Version @version@ built on @builddate@.</p>
<h2 id="overview">Release Notes for Vaadin @version@</h2>
<ul>
<li><a href="#overview">Overview</a></li>
<li><a href="#upgrading">General Upgrade Notes</a></li>
<li><a href="#upgrading-tk5">Instructions for Upgrading from IT Mill Toolkit 5</a></li>
<li><a href="#known-problems">Important known problems in Vaadin @version@</a></li>
<li><a href="#changelog">Change Log</a></li>
<li><a href="#requirements">Requirements</a></li>
</ul>
<p>Vaadin @version@ is an update release for Vaadin 6. In addition to various fixes, it
contains a number of significant enhancements.</p>
<ul>
<li>Enhanced keyboard navigation in <b>Table</b>, <b>Tree</b>, <b>DateField</b>, <b>Slider</b>, and many other components
<ul>
<li><p>In <b>Table</b> and <b>Tree</b> multiselect mode, selecting multiple items now requires pressing <b>Ctrl</b>. Use <tt>setMultiSelectMode()</tt> with MultiSelectMode.SIMPLE for multiselect without the <b>Ctrl</b> key. (<a href="http://dev.vaadin.com/ticket/3520">#3520</a>, <a href="http://dev.vaadin.com/ticket/4259">#4259</a>)</p></li>
</ul>
</li>
<li><b>Table</b> enhancements:
<ul>
<li>Footer - great for calculating sums, etc. Use <tt>setFooterVisible(true)</tt> to enable the footer and <tt>setColumnFooter()</tt> to set the footer text for a specific column. (<a href="http://dev.vaadin.com/ticket/1553">#1553</a>)</li>
<li>Header (<a href="http://dev.vaadin.com/ticket/4515">#4515</a>) and footer (<a href="http://dev.vaadin.com/ticket/4516">#4516</a>) click handlers</li>
<li><p>Column resize events (<b>ColumnResizeEvent</b>), which can be handled with <b>ColumnResizeListener</b></p></li>
</ul>
</li>
<li><p>Possibility for lazy loading of client-side components (aka GWT code splitting), which speeds up load times; see <a href="http://dev.vaadin.com/wiki/WidgetSet">more details</a></p>
<ul>
<li>In the rare case that you have extended the <b>DefaultWidgetSet</b> class, please notice that earlier, the custom entry point was defined in the <tt>.gwt.xml</tt> file as follows:
<pre> <entry-point class="com.example.MyExtendedWidgetSet" /></pre>
Now you need to write as follows:
<pre> <replace-with class="com.example.MyExtendedWidgetSet">
<when-type-is class="com.vaadin.terminal.gwt.client.WidgetSet" />
</replace-with></pre>
</li>
</ul>
</li>
<li><p>HTTP-level tester compatibility (JMeter, etc)</p></li>
<li><p><b>DateField</b> enhancements: input prompt and tab behavior</p></li>
<li><p>Indexed access to contained components in ordered layouts (<b>VerticalLayout</b>, <b>HorizontalLayout</b>, and <b>FormLayout</b>) with <tt>getComponentIndex()</tt> and <tt>getComponent(int index)</tt> (<a href="http://dev.vaadin.com/ticket/4609">#4609</a>)</p></li>
<li><p>Programmatic selection of text range in <b>TextField</b> with <tt>selectAll()</tt> and <tt>setSelectionRange()</tt>, and cursor positioning with <tt>setCursorPosition</tt> (<a href="http://dev.vaadin.com/ticket/5217">#5217</a>)</p></li>
<li><p>Ability to disable items in an <b>OptionGroup</b> with <tt>setItemEnabled()</tt> (<a href="http://dev.vaadin.com/ticket/3720">#3720</a>)</p></li>
</ul>
<p>In addition, there is a new <b>TreeTable</b> component (<a href="http://dev.vaadin.com/ticket/955">#955</a>). It is not yet included in the core library, but is <a href="http://vaadin.com/directory#addon/vaadin-treetable">available for download</a> from the Vaadin Directory.</p>
<p>See <a href="#changelog">Change Log</a> for a full list of tickets fixed in this release.</p>
<p>Problem fixes and enhancements planned for upcoming releases can be found from the <a
href="http://dev.vaadin.com/roadmap">Vaadin Roadmap</a> in Vaadin Trac.</p>
<p>As always, when upgrading from an earlier version, you should recompile any custom
widget sets and refresh your project in Eclipse. If you are upgrading from earlier than
6.3.0, notice that Vaadin 6.4 uses GWT 2.0 (included in the installation package). See
<a href="#upgrading">General Upgrade Notes</a> for more details on upgrading.</p>
<h2 id="widgetupgrade">Upgrading from an Earlier Version of Vaadin 6</h2>
<p>The way how widget sets are defined was simplified in Vaadin 6.2.
Existing projects, where custom widgets (a custom widget set) are used,
must be migrated when upgrading to Vaadin 6.2 or later. Projects where
the default widget set is used do not need migration. For most projects
this should be a quite painless upgrade.</p>
<p>
For applications where custom widgets are used (also applicable to widget projects):
<ul>
<li>Remove the <i>getTag()</i> method from all components and replace it with a <tt>@ClientWidget(VClientSideWidget.class)</tt> annotation. Tag names are no longer used to map the server-side and client-side part of the component. This is done automatically using the <tt>@ClientWidget</tt> annotation.</li>
<li>Remove the <tt>WidgetSet.java</tt> file. This file is no longer needed as the mapping between the server- and the client-side is done automatically using <tt>@ClientWidget</tt>.</li>
</ul>
</p>
<p>
If you are using widgets from another project (typically in a separate JAR file):
<ul>
<li>Acquire a new JAR which is compatible with Vaadin 6.3 and add it to <tt>WEB-INF/lib</tt>. The widget set compilation will automatically include the JAR in your <tt>.gwt.xml</tt> during compilation if you use the Eclipse <b>Compile Widget Set</b> button. For Ant/Maven you need to specify the location of the widget set JARs that you want to include in the application widget set.</li>
</ul>
</p>
<p>
If you package a widget set as a JAR for use in other projects:
<ul>
<li>Replace <tt>getTag()</tt> with <tt>@ClientWidget</tt> and remove the <tt>-WidgetSet.java</tt> as described above.</li>
<li>Add a "Vaadin-Widgetsets: <fully qualified name of widgetset>" (e.g. "Vaadin-Widgetsets: com.example.widgetset.mywidgetset") row to the META-INF/MANIFEST.MF of the JAR file. This enables the widget set builder to automatically detect and include the widget set in other projects.</li>
</ul>
</p>
<h2 id="upgrading">General Upgrade Notes</h2>
<p>When upgrading from an earlier version of the Vaadin library, you should always do the following:</p>
<ol>
<li>Install the new Vaadin JAR to your project</li>
<ul>
<li>If using the Vaadin Plugin in Eclipse, download and select the new version in project preferences.</li>
</ul>
<li>Install new GWT JARs if the GWT version has changed</li>
<ul>
<li>The Eclipse plugin will automatically download the new GWT and update launch configurations and the project build path when you update the Vaadin version.</li>
</ul>
<li>If you have custom widget sets, recompile them with the new Vaadin library using the included GWT compiler</li>
<li>If using the Eclipse IDE:
<ol type="a">
<li>Refresh the Eclipse project by selecting the project folder and pressing <strong>F5</strong></li>
<li>Restart the application server</li>
</ol>
</ol>
<p>Using the Vaadin project facet in the Eclipse IDE does the steps 1 and 2 automatically.</p>
<h2 id="upgrading-tk5">Instructions for Upgrading from IT Mill Toolkit 5</h2>
<p>While the Vaadin 6 API is otherwise mostly backward-compatible with IT Mill Toolkit 5.4, the
change of the product name has made it necessary to reflect it in the Java package names,
some name prefixes, and some other details.</p>
<h3>Server-side Upgrade Instructions</h3>
<ul>
<li>Java Package names have changed:</li>
<ul>
<li>In all Java files using IT Mill Toolkit, rename package prefix <tt>com.itmill.toolkit</tt> → <tt>com.vaadin</tt></li>
<li>You also need to update the <tt>web.xml</tt> deployment descriptor:</li>
<ul>
<li>The servlet class is now <strong>com.vaadin.terminal.gwt.server.ApplicationServlet</strong>.</li>
</ul>
</ul>
<li>Changes in themes:
<ul>
<li>Rename <tt>WebContent/ITMILL</tt> → <tt>WebContent/VAADIN</tt></li>
<ul>
<li>If you have extracted the built-in themes and widgetsets in IT Mill Toolkit JAR to the folder to have them served statically by the server, remove the old content and re-extract from Vaadin JAR.</li>
<li>This may require changes to build scripts for custom widgetsets, as well as to any code that relies on the old naming (it is discouraged but possible).</li>
</ul>
<li>The new "<tt>reindeer</tt>" theme is the default theme in Vaadin; the old
"<tt>default</tt>" theme in IT Mill Toolkit 5 has been renamed as "<tt>runo</tt>"</li>
<ul>
<li>There is no longer a theme with name "<tt>default</tt>"</li>
<li>In your custom theme, replace:
<table><tr><td></td><td><tt>@import "../default/styles.css";</tt></td></tr>
<tr><td align="right">→</td><td><tt>@import "../reindeer/styles.css";</tt></td><td>if you wish to use the new default theme,</td></tr>
<tr><td align="right">or →</td><td><tt>@import "../runo/styles.css";</tt></td><td>if you wish to use the old default theme.</td></tr></table></li>
<li>Use the new default theme with <tt>setTheme("reindeer")</tt> and the old one with <tt>setTheme("runo")</tt>.</li>
</ul>
<li>CSS class names now start with "<tt>v-</tt>" prefix instead of "<tt>i-</tt>"</li>
<ul>
<li>Search and replace "<tt>.i-</tt>" → "<tt>.v-</tt>" in custom themes </li>
</ul>
</ul>
<li>Embedding Vaadin applications in web pages:</li>
<ul>
<li>The name of the JavaScript variable used for launching applications has changed from "<tt>itmill.toolkitConfigurations</tt>" → "<tt>vaadin.vaadinConfigurations</tt>"</li>
</ul>
<li>Other changes in naming:</li>
<ul>
<li>Rename references to <tt>translateToolkitUri()</tt> → <tt>translateVaadinUri()</tt> method in <strong>ApplicationConnection</strong> class.
</ul>
</ul>
<h3>Client-side Upgrade Instructions</h3>
<p>The following changes are relevant only if you have developed or integrated custom
client-side widgets with Google Web Toolkit (GWT).</p>
<ul>
<li>GWT 2.0 is required for compiling custom widgets (optional)</li>
<ul>
<li>You need to upgrade GWT</li>
<li>The GWT Compiler class name has changed:</li>
<ul>
<li>Replace <tt>com.google.gwt.dev.GWTCompiler</tt> → <tt>com.google.gwt.dev.Compiler</tt> in your widget set build script (Ant) or launch configuration (Eclipse).</li>
<li>Replace the output directory argument for the compiler with the new WAR output argument: <tt>-out</tt> → <tt>-war</tt>. The directory parameter for the argument remains unchanged.</li>
</ul>
</ul>
<li>The "<strong>I</strong>" (IT Mill) prefix in client-side widget classes has been changed to "<strong>V</strong>" (Vaadin), for example: <strong>IButton</strong> → <strong>VButton</strong>.</li>
<li>Rename <strong>IToolkitOverlay</strong> → <strong>VOverlay</strong>
</ul>
<h2 id="gae">Notes and Limitations for Google App Engine</h2>
<p>The following instructions and limitations apply when you run a Vaadin application
under the Google App Engine.</p>
<ul>
<li><p>Applications must use <b>GAEApplicationServlet</b> instead of
<b>ApplicationServlet</b> in <tt>web.xml</tt>.</p></li>
<li><p>Session support must be enabled in <tt>appengine-web.xml</tt>:</p>
<pre> <sessions-enabled>true</sessions-enabled></pre>
</li>
<li><p>Avoid using the session for storage, usual App Engine limitations apply (no
synchronization, i.e, unreliable).</p></li>
<li><p>Vaadin uses memcache for mutex, the key is of the form
<tt>_vmutex<sessionid></tt>.</p></li>
<li><p>The Vaadin <b>WebApplicationContext</b> class is serialized separately into memcache
and datastore; the memcache key is <tt>_vac<sessionid></tt> and the datastore
entity kind is <tt>_vac</tt> with identifiers of the type <tt>_vac<sessionid></tt>.</p></li>
<li><p>DO NOT update application state when serving an <b>ApplicationResource</b> (e.g <b>ClassResource</b>.<i>getStream()</i>).</p></li>
<li><p>AVOID (or be very careful when) updating application state in a
<b>TransactionListener</b> or a <b>HttpServletRequestListener</b> - they are called even when the
application is not locked and won't be serialized (e.g <b>ApplicationResource</b>), and
changes can thus go missing (it should be safe to update things that can be safely discarded
later - i.e valid only for the current request)</p></li>
<li><p>The application remains locked during uploads - a progress bar is not possible</p></li>
</ul>
<h2 id="known-problems">Important known problems in Vaadin @version@</h2>
<ul>
<li><p><a href="http://dev.vaadin.com/ticket/1155">#1155</a>:
Uncompressing the installation package fails in Windows if using the
default Zip uncompression. Uncompression gives (in Windows Vista) an
error message about too long filenames, and a more obscure message in
other versions of Windows. Workaround: use <a
href="http://www.7-zip.org/">7-Zip</a> or some other good unzip
program for Windows.</p></li>
</ul>
<p>For other known problems, see open tickets at developer site <a
href="http://dev.vaadin.com/">dev.vaadin.com</a>.</p>
<h2 id="changelog">Change Log</h2>
<p>The following closed issues have been included in this release:</p>
<ul>
<li><a href="http://dev.vaadin.com/ticket/955">#955</a>: Tree table</li>
<li><a href="http://dev.vaadin.com/ticket/1086">#1086</a>: Tree: Keyboard navigation</li>
<li><a href="http://dev.vaadin.com/ticket/1553">#1553</a>: Table: add footer element</li>
<li><a href="http://dev.vaadin.com/ticket/2228">#2228</a>: Cannot get multiple causes from InvalidValueException</li>
<li><a href="http://dev.vaadin.com/ticket/2390">#2390</a>: Keyboard navigation for Table</li>
<li><a href="http://dev.vaadin.com/ticket/2497">#2497</a>: Missing icons</li>
<li><a href="http://dev.vaadin.com/ticket/2807">#2807</a>: Table should update column size back to server</li>
<li><a href="http://dev.vaadin.com/ticket/3161">#3161</a>: Reindeer black window rounded borders look pixelated in Chrome</li>
<li><a href="http://dev.vaadin.com/ticket/3520">#3520</a>: Improve Table multiselect to use Ctrl and Shift for selection</li>
<li><a href="http://dev.vaadin.com/ticket/3720">#3720</a>: Disable Items for OptionGroup</li>
<li><a href="http://dev.vaadin.com/ticket/3723">#3723</a>: ComponentContainerers should have the possibility to give an index of some component.</li>
<li><a href="http://dev.vaadin.com/ticket/4259">#4259</a>: Improve Tree multiselect to use Ctrl and Shift for selection</li>
<li><a href="http://dev.vaadin.com/ticket/4311">#4311</a>: DateField should not show stacktrace for invalid dates</li>
<li><a href="http://dev.vaadin.com/ticket/4315">#4315</a>: Window name generation should be deterministic</li>
<li><a href="http://dev.vaadin.com/ticket/4442">#4442</a>: Fix differences script to use zip instead of tar.gz for previous version</li>
<li><a href="http://dev.vaadin.com/ticket/4515">#4515</a>: Add support for Table header click handler</li>
<li><a href="http://dev.vaadin.com/ticket/4516">#4516</a>: Add support for Table footer click handler</li>
<li><a href="http://dev.vaadin.com/ticket/4576">#4576</a>: "Building of 6.4 branch fails with ""An exception has occurred in the compiler"""</li>
<li><a href="http://dev.vaadin.com/ticket/4595">#4595</a>: BeanItemContainer: no warning about use of Bean's hashCode</li>
<li><a href="http://dev.vaadin.com/ticket/4609">#4609</a>: Retrieving an index of a component in an AbstractOrderedLayout</li>
<li><a href="http://dev.vaadin.com/ticket/4631">#4631</a>: Implement Runo theme demo application</li>
<li><a href="http://dev.vaadin.com/ticket/5008">#5008</a>: Tree should ensure that the selected node is visible after navigation with the keyboard</li>
<li><a href="http://dev.vaadin.com/ticket/5012">#5012</a>: Self comparison of classId with itself in com.vaadin.ui.Embedded.setClassId(String)</li>
<li><a href="http://dev.vaadin.com/ticket/5024">#5024</a>: Table keyboard navigation blocks essential shortcuts</li>
<li><a href="http://dev.vaadin.com/ticket/5030">#5030</a>: ItemSetChangeEvent's in HierarchicalContainer are fired too early</li>
<li><a href="http://dev.vaadin.com/ticket/5057">#5057</a>: Keyboard support for TwinColSelect</li>
<li><a href="http://dev.vaadin.com/ticket/5061">#5061</a>: Keyboard support for MenuBar</li>
<li><a href="http://dev.vaadin.com/ticket/5063">#5063</a>: RichTextArea class should have constructors</li>
<li><a href="http://dev.vaadin.com/ticket/5065">#5065</a>: Table should not receive focus if it is not in selectable mode and all rows are visible</li>
<li><a href="http://dev.vaadin.com/ticket/5068">#5068</a>: When moving focus to Tree or Table keyboard nav focus should be placed to the current selection</li>
<li><a href="http://dev.vaadin.com/ticket/5099">#5099</a>: Slider keyboard navigation</li>
<li><a href="http://dev.vaadin.com/ticket/5102">#5102</a>: Double click in TwinColSelect should move selected item</li>
<li><a href="http://dev.vaadin.com/ticket/5104">#5104</a>: "Table with setNullSelectionAllowed(false) can be visually ""set to null"" using the keyboard"</li>
<li><a href="http://dev.vaadin.com/ticket/5112">#5112</a>: Table.focus() should not throw UnsupportedOperationException</li>
<li><a href="http://dev.vaadin.com/ticket/5114">#5114</a>: ClassPathExplorer should not use URL instances as map or set keys</li>
<li><a href="http://dev.vaadin.com/ticket/5120">#5120</a>: TableClickHandlers sample has extra scrollbar</li>
<li><a href="http://dev.vaadin.com/ticket/5144">#5144</a>: Moving the caret inside a textfield which is inside a selectable Table is impossible</li>
<li><a href="http://dev.vaadin.com/ticket/5174">#5174</a>: Menu cannot be clicked using mouse</li>
<li><a href="http://dev.vaadin.com/ticket/5177">#5177</a>: Popup for DateField with msec resolution fails to open after entering invalid date</li>
<li><a href="http://dev.vaadin.com/ticket/5179">#5179</a>: TabSheet should have a removeTab(Tab t)</li>
<li><a href="http://dev.vaadin.com/ticket/5182">#5182</a>: ComponentLocator fails to identify widgets attached to RootPanel</li>
<li><a href="http://dev.vaadin.com/ticket/5203">#5203</a>: DateField setResolution() should call requestRepaint</li>
<li><a href="http://dev.vaadin.com/ticket/5217">#5217</a>: Text selections/cursor position features</li>
</ul>
<h2 id="requirements">Requirements</h2>
<p>Vaadin is available for the following operating systems:</p>
<ul>
<li>Windows (see the Zip installation notice above)</li>
<li>Linux</li>
<li>Mac OS X Tiger (mac) or Leopard (leopard)</li>
<li>Other UNIX operating systems, such as Sun Solaris</li>
</ul>
<p>Vaadin supports Java Servlet API 2.3 and later versions and should work with
any Java application server that conforms to the standard. It supports the following
application servers:</p>
<ul>
<li>Apache Tomcat, version 4.1 or later</li>
<li>BEA WebLogic® Server, version 9.2 or later</li>
<li>IBM WebSphere® Application Server, version 6.1 or later</li>
<li>JBoss Application Server, version 3.2.8 or later</li>
<li>Jetty, version 5 or later</li>
<li>Glassfish, version 2 or later</li>
</ul>
<p>Vaadin supports the following browsers for using the applications made with
it:</p>
<ul>
<li>Mozilla Firefox 3</li>
<li>Internet Explorer releases 6, 7, and 8</li>
<li>Safari 3 and 4</li>
<li>Opera 10</li>
<li>Google Chrome (latest version)</li>
</ul>
<p>The support for browsers follows the support by GWT. The browsers are supported on both
Windows and Mac, if available. Firefox is supported also on Linux. There may be differences between the
exact versions of the supported browsers that may cause incompatibility with applications
made with Vaadin.</p>
<p>The following browsers are not supported but have been found to
work to a large degree:</p>
<ul>
<li>Safari 2</li>
<li>Firefox 2</li>
<li>Older versions of Google Chrome</li>
<li>iPhone (firmware 2.2)</li>
<li>Midori (0.1.2)</li>
<li>Epiphany (2.22.3), Galeon, and other Gecko-based browsers. Also WebKit-based Epiphany (2.22.3) works.</li>
<li>Konqueror 4.2 (3.5.x does not work)</li>
<li>Nokia Internet Tablet N800 and N810 (ITOS 2008, Opera-based browser).</li>
</ul>
<p>The reported versions are those that have been tested, though other versions may work
as well.</p>
<p>Nokia E-series phones, such as E90, have been known to work with older versions, but
not with Vaadin 6. Links, Lynx, and other text-based browsers do not
work.</p>
</div> <!-- /content-->
<div id="footer">
<span class="slogan"><strong>vaadin <em>}></em></strong> thinking of U and I<span> <a href="#top">↑ Back to top</a>
</div> <!-- /footer -->
</body>
</html>
|
