From 1ff484c4c69266b98f63c7356bcc2354d2baff71 Mon Sep 17 00:00:00 2001 From: Marko Gronroos Date: Tue, 29 Jan 2013 15:45:10 +0200 Subject: [PATCH] Updated Release Notes for Vaadin 7.0.0. #10861 Change-Id: I2d428757b62a8bf02d9e898794374ec46a92841b --- WebContent/release-notes.html | 1011 +++++++++++++++++++++++++++++++-- 1 file changed, 966 insertions(+), 45 deletions(-) diff --git a/WebContent/release-notes.html b/WebContent/release-notes.html index 83ad43850b..3b928d7094 100644 --- a/WebContent/release-notes.html +++ b/WebContent/release-notes.html @@ -114,8 +114,8 @@

Enhancements in Vaadin @version@

- The @version@ includes many fixes and smaller features and changes. The following - major changes were introduced in the earlier @version-minor@ releases: + The @version@ includes many major and minor enhancements and changes. Below is a + list of the most notable changes:

+
  • Applications are now written by extending the UI class instead of the Application class + +
    • +
  • The Application class is removed altogether + +
    • +
  • The current UI, Page, VaadinServlet, VaadinService, and VaadinSession can be accessed globally with a static getCurrent() method. The instance is a ThreadLocal object for the currently processed request.
    • +
  • The Window now only has the meaning of a floating sub-window inside browser window
    • +
  • The Panel and Windowno longer extend ComponentContainer, + but SingleComponentContainer, which has no addComponent() method + +
    • +
  • Popup windows can no longer be opened directly from code, but by using a BrowserWindowOpener extension which can be attached to any component
  • Navigation API for view navigation
    • -
  • Component and UI extensions
    • -
  • Resource loading (JS/CSS) by the framework
    • +
  • Component and UI extensions are now possible
  • Complete overhaul of the client-server communication architecture
    • -
  • Form is deprecated and form hand is replaced with the FieldGroup
    • -
  • Get computed style of a component from the browser
    • -
  • Support for border, padding, and margin in core layout components
    • -
  • Applications are now written by extending the UI class - -
    • -
  • The Application class is removed altogether - +
  • Form is deprecated and form data binding is replaced with the new FieldGroup +
    • +
  • The LoginForm component is now deprecated because of unreliable support in browsers
  • Themeing is now done with Sass
    • -
  • Add-ons can modify the startup page
  • All addListener() methods have changed to listener-specific methods, such as addClickListener(), addValueChangeListener(), etc.
    • +
  • UriFragmentListener changed to UriFragmentChangedListener
    • +
  • UriHandler and ParameterHandler replaced with RequestHandler
    • +
  • Resource loading (JS/CSS) by the framework
  • Packaging has changed, now in a ZIP package (see Package Contents above)
    • -
  • The Panel and Window (and in UI in early betas) no longer - extend ComponentContainer, but SingleComponentContainer, which has - no addComponent() method - -
    • +
  • Add-ons can modify the startup page
    • +
  • You can get the computed style of a component from the browser
    • +
  • Support for border, padding, and margin in core layout components
  • The ColorPicker component is now included in the Vaadin core framework
    • -
  • Sass compiler can now be used in client-side projects.
    • @@ -199,7 +219,9 @@

    There are many other enhancements. Most of them are described in more detail in the mini-tutorials in - the Vaadin Wiki. + the Vaadin Wiki. Also see the Vaadin + 6 to 7 Migration Guide.

    Limitations

    @@ -213,18 +235,908 @@

    ChangeLog

    - For a complete list of changes in this release, please see the list - of closed tickets. + Below is the complete list of closed tickets in Vaadin 7. You can also query the tickets by all the milestones and filter out the defects and tasks from the query to list only actual enhancements.

    +

    The features voted at the Vaadin Pro Account are marked in the list.

    + + + + +

    Migrating from Vaadin 6

    All Vaadin 6 applications need some changes when migrating to Vaadin 7. The most obvious changes are in the application/window API and require extending either UI or UI.LegacyApplication instead of Application. A detailed - list of migration changes are given in the Vaadin 7 Migration - Guide. + list of migration changes are given in the Vaadin + 7 Migration Guide.

    @@ -253,8 +1165,7 @@

    - The dependencies are listed in the Vaadin Framework Terms and - Conditions. Some are explicit dependencies packaged and distributed as + The dependencies are listed in the Licensing description. Some are explicit dependencies packaged and distributed as separate JARs, while some are included inside other libraries.

    @@ -270,10 +1181,20 @@

    Upgrading the Eclipse Plugin

    +

    + Vaadin 7 requires that you use a compatible version of the Vaadin Plugin for + Eclipse. The stable version of the plugin is available from the + http://vaadin.com/eclipse update site. Please see the section + about updating the plugin in the Book of Vaadin and the installation instructions at the download + site for more details. +

    +

    - This release requires that you use the experimental Vaadin Plugin for + You can also use the experimental Vaadin Plugin for Eclipse. Its update site is - http://vaadin.com/eclipse/experimental. Please see the installation instructions for more details. + http://vaadin.com/eclipse/experimental.

    General Upgrading Instructions

    -- 2.39.5