<li>Complete overhaul of the client-server communication architecture
<ul>
<li>All add-on components that have widgets need to be ported to Vaadin 7</li>
- <li>Integration of a GWT widget is done in a <i>connector</i> class
- <ul>
- </ul>
- </li>
+ <li>Integration of a GWT widget is done in a <i>connector</i> class</li>
<li>Component-to-widget mapping now defined on the client-side, in the connector</li>
<li>No more <b style="text-decoration: line-through">Paintable</b> or <b style="text-decoration: line-through">VariableOwner</b>
<li>Server-side component and client-side widget can have a <emphasis>shared state</emphasis> object which is automatically synchronized</li>
<p>
For a complete list of changes in this release, please see the <a
- href="http://dev.vaadin.com/query?status=closed&group=resolution&milestone=Vaadin+7.0.0.alpha1">list
+ href="http://dev.vaadin.com/query?status=closed&group=resolution&milestone=Vaadin+7.0.0.alpha2">list
of closed tickets</a>.
</p>
<b>Root</b> or <b>Root.LegacyApplication</b> instead of <b>Application</b>.
</p>
+ <para>
+ Vaadin 6 add-ons (ones that contain widgets) do not work in Vaadin 7 - please
+ check the add-ons in <a href="http://vaadin.com/directory/">Vaadin Directory</a>
+ for Vaadin 7 support.
+ </p>
+
+ <p>
+ Any custom client-side widgets need to be changed to use the new client-server
+ communication API or the Vaadin 6 compatibility API.
+ </p>
+
<p>
A detailed list of migration changes are given in the <a
href="http://dev.vaadin.com/wiki/Vaadin7/MigrationGuide">Vaadin 7 Migration
</p>
<ul>
- <li>Windows (see the <a href="#knownissues">Zip installation
- notice above</a>)</li>
+ <li>Windows</li>
<li>Linux</li>
<li>Mac OS X</li>
</ul>
</p>
<ul>
- <li>Mozilla Firefox 10</li>
+ <li>Mozilla Firefox 11</li>
<li>Internet Explorer 8-9</li>
<li>Safari 5</li>
<li>Opera 11</li>
- <li>Google Chrome 16</li>
+ <li>Google Chrome 18</li>
</ul>
<h2 id="vaadinontheweb">Vaadin on the Web</h2>