From: Marko Grönroos Date: Thu, 24 Sep 2009 11:24:14 +0000 (+0000) Subject: Release Notes for Vaadin 6.1.1. X-Git-Tag: 6.7.0.beta1~2463^2~12 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=330414001f113ef25338e23a8dc3648f8df147bf;p=vaadin-framework.git Release Notes for Vaadin 6.1.1. svn changeset:8901/svn branch:6.1 --- diff --git a/WebContent/release-notes.html b/WebContent/release-notes.html index 97ae24c73e..13f341524f 100644 --- a/WebContent/release-notes.html +++ b/WebContent/release-notes.html @@ -25,120 +25,50 @@ -

Vaadin @version@ is the first feature update release for Vaadin 6. In addition to many bug -fixes, the most significant additions are:

+

Vaadin @version@ is a bugfix release for Vaadin 6. See the Change +Log below for a detailed list of issues fixed in this release.

- +

For a list of new features and enhancements in the previous minor update release 6.1.0, +see the Release +Notes for Vaadin 6.1.0.

-

See the Change Log below for a more detailed list of closed issues in this release.

+

Problem fixes and enhancements planned for upcoming releases can be found from the Vaadin Roadmap in Vaadin Trac.

-

Vaadin @version@ uses Google Web Toolkit 1.7.0, which is included in the gwt folder of the installation package. The plugin downloads the new version automatically (you may need to update your widget set compilation scripts and launch configurations).

+

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.1.0, notice that Vaadin 6.1 uses GWT 1.7.0 (included in the installation package). See +General Upgrade Notes for more details on upgrading.

+ +

Change Log

+ +

The following issues have been fixed in this release:

-

Button Component Modifications

-

The previous version of the VButton widget (i.e. GWT counterpart for the Button component) was built using the native BUTTON element in the browser. Because of multiple theming issues that resulted from that (final nail in the coffin, #3079), the implementation was changed to a DIV based one.

-

For the Runo theme this means that your application buttons will change their style when you update to 6.1. See the migration instructions for more help. -

The previous version is now included as a new component called NativeButton, and it is always rendered with the native BUTTON element in the client side and will contain no additional styling.

-

You shouldn't notice this change in any way, unless you've made modifications to the button CSS in a custom theme, or you're using the Runo theme. Below are listed the most important changes you need to consider.

-

Implications to Custom Themes: Migration Guide

-

If you've made additional styling to buttons in your custom theme, you may need to make changes both to your Java and CSS code.

-
- - - - - -
-

Runo theme

- Unmodified Buttons -
    -
  • If you prefer the original, native button look, change all buttons in your application from Button to NativeButton.
    • -
- Themed Buttons -
    -
  • Replace the Button with NativeButton
    • -
  • In your theme CSS, find-and-replace
    .v-button → .v-nativebutton
    • -
- 		-

Reindeer theme

- Unmodified Buttons -
    -
  • No actions are needed.
    • -
- Buttons with a completely different theme -
    -
  • Replace the Button with NativeButton
    • -
  • In your theme CSS, find-and-replace
    .v-button → .v-nativebutton
    • -
- Buttons with some theme modifications/additions -

We cannot provide a comprehensive migration guide for these situations, since every case will most likely require different actions.

-

But if your modified buttons looks broken, it is most likely caused by the new additional element in the HTML structure (span.v-button-wrap). Most of the styles previously applied on .v-button-caption have been moved to .v-button-wrap, so be sure to change your CSS accordingly.

-
-

-And if all else fails, you're always welcome to ask further questions on our forum, we're there to help. -

-
-

General Upgrade Notes

When upgrading from an earlier version of the Vaadin library, you should always do the following:

@@ -316,100 +246,6 @@ sets with the regular Vaadin package for your platform.

For other known problems, see open tickets at developer site dev.vaadin.com.

-

Change Log

- -

The following issues have been fixed in this release:

- - -

Requirements

Vaadin is available for the following operating systems: