123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405 |
- <!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 6</title>
- <link rel="stylesheet" type="text/css" href="demo/css/styles.css" />
- <!--[if IE]>
- <link rel="stylesheet" type="text/css" href="demo/css/ie.css" />
- <![endif]-->
- </head>
- <body>
-
- <div id="header">
- <h1>Vaadin – thinking of U and I</h1>
- <div id="version">
- <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>
-
- <b><i>This is a prerelease version of the upcoming Vaadin 6.3 release.
- Samples and documentation are still incomplete. There may be bugs, even
- critical ones, please help us to find them.</i></b>
-
- <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>Drag-and-Drop support (<a href="http://dev.vaadin.com/ticket/119">#119</a>)</li>
- <ul>
- <li>Dragging <b>Tree</b> and <b>Table</b> items as well as entire components</li>
- <li>See the Sampler for Drag-and-Drop examples and Book of Vaadin for more detailed instructions</li>
- </ul>
-
- <li>GWT 2.0</li>
- <ul>
- <li>Platform independent and a new development mode.</li>
- <li>No more separate OOPHM - the GWT Development Mode uses a browser
- plugin to allow debugging directly in the supported browsers</li>
- </ul>
-
- <li>New protected <tt>attachField()</tt> method in <b>Form</b> allows customizing
- the form layout according to item identifier and object type.
- For example, you could lay check boxes horizontally. (<a href="http://dev.vaadin.com/ticket/2205">#2205</a>)</li>
-
- <li><tt>Form</tt> no longer resets the field caption set by the <tt>FormFieldFactory</tt></li>
-
- <li>Easier shortcut key binding</li>
- <ul>
- <li>Bind shortcuts to directly to buttons by using <tt>setClickShortcut()</tt></li>
- <li>Bind field components by adding a <b>FocusShortcut</b> as a shortcut listener to a component with <tt>addShortcutListener()</tt></li>
- <li>Shortcuts can be scoped to a <b>Panel,Window</b> or <b>Form</b> by adding them with <tt>addAction()</tt> to the component</li>
- </ul>
-
- <li>ISO-8601 week numbers in <b>DateField</b>s (<a href="http://dev.vaadin.com/ticket/3492">#3492</a>)</li>
-
- <li>Customizable system messages to warn about disabled cookies</li>
-
- <li>Methods for browser detection on server side (<a href="http://dev.vaadin.com/ticket/3931">#3931</a>)</li>
-
- <li>Filtering support for <tt>HierarchicalContainer</tt></li>
-
- <li>ApplicationServlet provides timestamps for static resources to improve browser caching support</tt></li>
-
- <li>Portlet 2.0 <tt>PortletListener</tt> now includes the active <tt>Window</tt> in all methods for improved multi-window support in portlets (<a href="http://dev.vaadin.com/ticket/4188">#4188</a>)</li>
-
- <li>Focus and blur listeners for <tt>Button,NativeButton,CheckBox,OptionGroup</tt></li>
-
- <li>Many bug fixes including many minor errorneous behavior fixes for containers</li>
- </ul>
-
- <p>See <a href="#changelog">Change Log</a></li> 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.3 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/119">#119</a>: Design drag and drop support API</li>
- <li><a href="http://dev.vaadin.com/ticket/875">#875</a>: Keybinding for any components should be easier to do</li>
- <li><a href="http://dev.vaadin.com/ticket/2205">#2205</a>: Make Form layouting more flexible</li>
- <li><a href="http://dev.vaadin.com/ticket/2586">#2586</a>: Theme should be refreshed when Vaadin version is updated</li>
- <li><a href="http://dev.vaadin.com/ticket/3467">#3467</a>: Button styles missing? (Button.STYLE_LINK exists, but others not)</li>
- <li><a href="http://dev.vaadin.com/ticket/3492">#3492</a>: DateField should have an option to show week numbers</li>
- <li><a href="http://dev.vaadin.com/ticket/3554">#3554</a>: Form.addItemProperty() resets caption created by FieldFactory</li>
- <li><a href="http://dev.vaadin.com/ticket/3734">#3734</a>: Widgetset fails to load when customized system messages contain special characters</li>
- <li><a href="http://dev.vaadin.com/ticket/3736">#3736</a>: Split up style and type definitions</li>
- <li><a href="http://dev.vaadin.com/ticket/3810">#3810</a>: Upgrade GWT to 2.0</li>
- <li><a href="http://dev.vaadin.com/ticket/3913">#3913</a>: Focus and BlurEvents for Button/Checkbox and OptionGroup</li>
- <li><a href="http://dev.vaadin.com/ticket/3931">#3931</a>: Provide methods for browser detection in WebBrowser</li>
- <li><a href="http://dev.vaadin.com/ticket/3940">#3940</a>: Setter for CustomLayout template contents</li>
- <li><a href="http://dev.vaadin.com/ticket/3949">#3949</a>: Add a convenience removeItemAndChildren method to HierarchicalContainer and ContainerHierarchicalWrapper</li>
- <li><a href="http://dev.vaadin.com/ticket/3984">#3984</a>: CustomLayout "not found" debug message should indicate where it looked</li>
- <li><a href="http://dev.vaadin.com/ticket/3994">#3994</a>: Remove extra dependencies from DefaultWidgetSet</li>
- <li><a href="http://dev.vaadin.com/ticket/4085">#4085</a>: Table height is miscalculated (IE6)</li>
- <li><a href="http://dev.vaadin.com/ticket/4102">#4102</a>: RichTextArea should provide feedback on current text format</li>
- <li><a href="http://dev.vaadin.com/ticket/4106">#4106</a>: BeanItemContainer slow in some instances</li>
- <li><a href="http://dev.vaadin.com/ticket/4107">#4107</a>: Multi-selectable AbstractSelect considers itself to be non-empty when nothing is selected</li>
- <li><a href="http://dev.vaadin.com/ticket/4128">#4128</a>: Allow custom servlets to send critical notifications to client</li>
- <li><a href="http://dev.vaadin.com/ticket/4129">#4129</a>: Show a message if cookie support is disabled in the browser</li>
- <li><a href="http://dev.vaadin.com/ticket/4139">#4139</a>: Update RichTextAreaToolbar to GWT 2.0</li>
- <li><a href="http://dev.vaadin.com/ticket/4170">#4170</a>: IndexedContainer.addItemAfter(null, Object) does not work</li>
- <li><a href="http://dev.vaadin.com/ticket/4188">#4188</a>: PortletListener cannot know which window the request is using</li>
- <li><a href="http://dev.vaadin.com/ticket/4192">#4192</a>: HierarchicalContainer implements Container.Filterable but does not allow filtering</li>
- <li><a href="http://dev.vaadin.com/ticket/4240">#4240</a>: Remove URIFragmentUtility workaround (#4099)</li>
- <li><a href="http://dev.vaadin.com/ticket/4241">#4241</a>: Implement drag'n'drop support for Table</li>
- <li><a href="http://dev.vaadin.com/ticket/4242">#4242</a>: Implement drag'n'drop support for Tree</li>
- <li><a href="http://dev.vaadin.com/ticket/4249">#4249</a>: IndexedContainer.addItemAfter(Object) should return item id, not item</li>
- <li><a href="http://dev.vaadin.com/ticket/4250">#4250</a>: IndexedContainer.nextItemId should return null for item ids not in container</li>
- <li><a href="http://dev.vaadin.com/ticket/4279">#4279</a>: RichTextEditor does not save contents on Chrome and Safari</li>
- <li><a href="http://dev.vaadin.com/ticket/4284">#4284</a>: Add Chrome version parsing to BrowserInfo</li>
- <li><a href="http://dev.vaadin.com/ticket/4286">#4286</a>: RichTextArea IE workaround causes assertion error in GWT development mode</li>
- <li><a href="http://dev.vaadin.com/ticket/4292">#4292</a>: removeItem in Container.Hierarchical implementations should handle orphaned children</li>
- <li><a href="http://dev.vaadin.com/ticket/4293">#4293</a>: ContainerHierarchicalWrapper.setParent() creates "duplicates" into the hierarchy</li>
- <li><a href="http://dev.vaadin.com/ticket/4299">#4299</a>: Suboptimal row cache update in Table</li>
- <li><a href="http://dev.vaadin.com/ticket/4300">#4300</a>: Fix standard DnD drop hints</li>
- <li><a href="http://dev.vaadin.com/ticket/4303">#4303</a>: BeanItemContainer.addItemAfter(null, Object) does not work</li>
- <li><a href="http://dev.vaadin.com/ticket/4322">#4322</a>: Tree drop indicator flickers and shows the wrong target</li>
- <li><a href="http://dev.vaadin.com/ticket/4334">#4334</a>: TextField contents offset in Firefox 3.6</li>
- <li><a href="http://dev.vaadin.com/ticket/4347">#4347</a>: Mouse cursor should not change during a drag'n'drop operation</li>
- <li><a href="http://dev.vaadin.com/ticket/4350">#4350</a>: Removing a root recursively puts HierarchicalContainerWrapper in an inconsistent state</li>
- <li><a href="http://dev.vaadin.com/ticket/4352">#4352</a>: Vaadin application font is ugly in Windows Safari/Chrome</li>
- <li><a href="http://dev.vaadin.com/ticket/4354">#4354</a>: SplitPanel setComponent methods should check if the component is already set</li>
- <li><a href="http://dev.vaadin.com/ticket/4359">#4359</a>: Immediate upload in a wide form layout does not work in Firefox 3.5 and Opera</li>
- <li><a href="http://dev.vaadin.com/ticket/4360">#4360</a>: HierarchicalContainer.setParent() creates "duplicates" into the hierarchy</li>
- <li><a href="http://dev.vaadin.com/ticket/4362">#4362</a>: Sub windows don't obey setPositionX/Y if only one is set</li>
- <li><a href="http://dev.vaadin.com/ticket/4365">#4365</a>: When dragging components, drop target is null for WrapperDropDetails</li>
- <li><a href="http://dev.vaadin.com/ticket/4370">#4370</a>: HierarchicalContainer.setParent() removes node children incorrectly</li>
- <li><a href="http://dev.vaadin.com/ticket/4394">#4394</a>: ValueChangeListener is called multiple times for fields</li>
- <li><a href="http://dev.vaadin.com/ticket/4395">#4395</a>: HTML5 Drag and Drop example gives Internal Error on Safari</li>
- <li><a href="http://dev.vaadin.com/ticket/4396">#4396</a>: RichTextArea broken in IE</li>
- <li><a href="http://dev.vaadin.com/ticket/4399">#4399</a>: AbstractApplicationServlet.RequestType enum should have visibility protected</li>
- <li><a href="http://dev.vaadin.com/ticket/4401">#4401</a>: Clicking on week numbers in VCalendarPanel selects a date</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>
|