From 330414001f113ef25338e23a8dc3648f8df147bf Mon Sep 17 00:00:00 2001
From: =?utf8?q?Marko=20Gr=C3=B6nroos?= 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. The following issues have been fixed in this release: 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. 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. 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 (
-And if all else fails, you're always welcome to ask further questions on our forum, we're there to help.
- When upgrading from an earlier version of the Vaadin library, you should always do the following:
-
-
+
-
-
-
- Change Log
+
+Button Component Modifications
-
-
-v-nativebutton
.
-
-
-
-
-
- VButton widget structure
- div.v-button
- span.v-button-wrap
- [span.v-errorindicator]
- [img.v-icon]
- span.v-button-caption
-
-
- VNativeButton widget structure
- button.v-nativebutton
- [span.v-errorindicator]
- [img.v-icon]
- span.v-nativebutton-caption
- Implications to Custom Themes: Migration Guide
-
-
-
-
-
-
- Runo theme
- Unmodified Buttons
-
-
- Themed Buttons
-
-
- .v-button
→ .v-nativebutton
-
- Reindeer theme
- Unmodified Buttons
-
-
- Buttons with a completely different theme
-
-
- Buttons with some theme modifications/additions
- .v-button
→ .v-nativebutton
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.General Upgrade Notes
For other known problems, see open tickets at developer site dev.vaadin.com.
-The following issues have been fixed in this release:
- -Vaadin is available for the following operating systems:
-- 2.39.5