From: Marko Grönroos Date: Fri, 18 Dec 2009 13:22:16 +0000 (+0000) Subject: Mostly language corrections to the Release Notes for Vaadin 6.2. Sorted the change... X-Git-Tag: 6.7.0.beta1~2095^2~2 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=88a0a7b8163eb02e495f61f578f2d7850b592e4c;p=vaadin-framework.git Mostly language corrections to the Release Notes for Vaadin 6.2. Sorted the change list. svn changeset:10433/svn branch:6.2 --- diff --git a/WebContent/release-notes.html b/WebContent/release-notes.html index 15bb87bd30..efa1f4b22f 100644 --- a/WebContent/release-notes.html +++ b/WebContent/release-notes.html @@ -82,9 +82,9 @@ public class ColorPicker extends AbstractField {
  • Typed arrays and maps can now be sent to server with updateVariable()
    • @@ -104,40 +104,40 @@ public class ColorPicker extends AbstractField {
  • Improved event support
  • JavaScript execution with Window.excecuteJavaScript()
  • Additional Maven archetypes
  • Maven Vaadin plugin
  • HttpServletRequestListener
  • PortletRequestListener
  • Enhancements to various components:
  • Automatic integration tests
    • @@ -155,32 +155,32 @@ widget sets and refresh your project in Eclipse. If you are upgrading from earli 6.2.0, notice that Vaadin 6.2 uses GWT 1.7.0 (included in the installation package). See General Upgrade Notes for more details on upgrading.

    -

    Upgrading from an Earlier Vaadin 6 version

    +

    Upgrading from an Earlier Version of Vaadin 6

    -The widgetsets have been renewed and simplified in Vaadin 6.2 as described above. Existing projects -where custom widgets (a custom widgetset) are used must be migrated when upgrading to Vaadin 6.2. -Projects where the default widgetset is used do not need migration. For most +The way how widget sets are defined has been simplified in Vaadin 6.2, as described above. Existing projects, +where custom widgets (a custom widget set) are used, must be migrated when upgrading to Vaadin 6.2. +Projects where the default widget set is used do not need migration. For most projects this should be a quite painless upgrade.

    For applications where custom widgets are used (also applicable to widget projects):

    If you are using widgets from another project (typically in a separate JAR file):

    If you package a widget set as a JAR for use in other projects:

    @@ -374,94 +374,94 @@ sets with the regular Vaadin package for your platform.

    The following closed issues have been included in this release:

    Requirements