From 94f6a844627cbba41a6f1e980d1f08bedfcb3ef5 Mon Sep 17 00:00:00 2001 From: Marko Grönroos Date: Tue, 7 Apr 2009 13:50:23 +0000 Subject: Merge from versions/5.4 to versions/6.0: Merged [7302]: Removed obsolete testing scripts for Testing Tools 1.0. Merged [7305]: Initial testing tools target, doesn't quite work yet, demo launching is missing, etc. Merged [7321]: Moved build/docbook directory from 5.4 branch to doc tree. Merged [7325]: Moved XEP directory from 5.4 branch to doc tree. Merged [7333]: Removed all manual related material and build instructions from regular toolkit branch. Merged [7342]: Building manual from the toolkit build script. Merged [7343]: Fixed a namespace problem in build file and organized clean-up targets a little. Merged [7346]: Removed the obsolete DTDs. Merged [7348]: Changed and tags in some HTML and text files to @...@ notation to avoid some validation errors in Eclipse. svn changeset:7352/svn branch:6.0 --- WebContent/index.html | 4 +- WebContent/release-notes.html | 242 +----------------------------------------- 2 files changed, 4 insertions(+), 242 deletions(-) (limited to 'WebContent') diff --git a/WebContent/index.html b/WebContent/index.html index 61121b78ef..cd5b6dd5df 100644 --- a/WebContent/index.html +++ b/WebContent/index.html @@ -164,14 +164,14 @@

» Package contents

- Version + Version @version@
Library

Contains all you need to start a new Toolkit project (binaries, sources, default - themes and widgetsets). Toolkit JAR

+ themes and widgetsets). Toolkit JAR

diff --git a/WebContent/release-notes.html b/WebContent/release-notes.html index 3ed8e8f259..22319c3147 100644 --- a/WebContent/release-notes.html +++ b/WebContent/release-notes.html @@ -25,250 +25,12 @@ support site forum.itmill.com
-

Release Notes for IT Mill Toolkit Version

+

Release Notes for IT Mill Toolkit Version @version@

Version 5.3.0 is the first stable release of IT Mill Toolkit 5, meaning that there are no known major problems and the API will be kept backward compatible.

-

Google Web Toolkit Upgraded -to Version 1.5

- -

The GWT used in IT Mill Toolkit is upgraded to version 1.5. If -you have made your own client side components, you will need to upgrade -your GWT library. Many things have changed in GWT 1.5, but upgrading is -rather straightforward and, as a bonus, you will get the nice features -from Java 1.5. For more details on GWT 1.5, see the GWT -web site.

- -

Java 5 Now Required

- -

As GWT now requires Java 5, support for Java 1.4 is discontinued -also in IT Mill Toolkit.

- -

IT Mill Toolkit supports the Sun Microsystems JDK and JRE, though others should work as -well. When running the demo application, the Jetty web server may produce errors in the -console if using certain other Java implementations, especially the GNU JRE.

- -

Debug Mode Enabled by Default

- -

The debug mode is now enabled by default, to allow debugging -layout and other problems more easily. The debug mode:

- -
    -
  • Displays debug data to the server console/log.
    • - -
  • Allows showing the client-side logging window, which you can - enable by adding the request parameter "?debug=true" to the - application URI.
    • - -
  • "Analyze layouts" -button in the debug window runs basic - checks on usage of relative units. Potentially problematic layouts will - be shown in the debug window and in System.out.
    • -
- -

You should disable the debug mode when releasing your application -for production use. You can do this by including the following setting -in your web.xml.

- -
  <context-param>
-  	<param-name>productionMode</param-name>
-  	<param-value>true</param-value>
-  	<description>IT Mill Toolkit production mode</description>
-  </context-param>
-
- -

Layout Changes

- -

The stable IT Mill Toolkit version 5.3 introduces a major rework -of layout components since the beta versions 5.2.x and before.

- -

Major changes include:

- -
    -
  • Layouts are stricter than before - usage of debug mode - during development is recommended. Use "Analyze layouts" in client side - debug window if you encounter problems with relative size.
    • -
  • VerticalLayout and HorizontalLayout obsolete - OrderedLayout
    • -
  • Layout cell alignment has changed
    • -
  • ExpandLayout deprecated
    • -
  • Default sizes have changed
    • -
- -

OrderedLayout deprecated

- -

VerticalLayout and HorizontalLayout replace the old -OrderedLayout, which is now deprecated.

- -

Essentially, this makes the creation of these basic layouts a bit -tidier as you don't have to give the orientation as an ugly parameter to -the constructor. You won't be able to change the orientation with setOrientation() -any longer, though such need is rare anyhow.

- -

Layout Cell Alignment Changed

- -

Previously, the alignment of components within layout cells was set with -setComponentAlignment() with constants for OrderedLayout (now -VerticalLayout and HorizontalLayout) and GridLayout separately, such -as OrderedLayout.ALIGNMENT_TOP_LEFT. Now the method takes constants defined in -Alignment.

- -

For example, aligning a component "top left" is now:

- -
mylayout.setComponentAlignment(mycomponent, Alignment.TOP_LEFT);
- -

You can also give an Alignment object as a parameter and give horizontal and -vertical alignment separately with bitmask parameters.

- -

Handling -of relative sizes has changed, ExpandLayout deprecated

- -

ExpandLayout is deprecated. You can now define the -relative sizes of components more flexibly with setExpandRatio() -method available in VerticalLayout or HorizontalLayout.

- -

See the article on Relative -sizes in IT Mill Toolkit for details.

- -

Some components now have -default sizes

- -

Previously, almost all components had undefined size by default. -Now some containers have 100% width by default. These components are:

- -
    -
  • VerticalLayout
    • -
  • Window
    • -
  • Panel
    • -
  • TabSheet
    • -
  • SplitPanel (note that SplitPanel also has 100% - height by default)
    • -
  • Form
    • -
  • FormLayout
    • -
  • Label
    • -
- -

If the width of a Label is set defined, as is now the default, the label text -will wrap appropriately, but if it is set as undefined, the text will never wrap.

- -

Miscellaneous Layout Changes

- -
    -
  • You can now give component alignments inside layouts easily - with setComponentAlignment() as a string, such as "top - left" or "m,c" (for middle-center). See #2279.
    • - -
  • Form no longer copies all components from the old - layout to the new one when doing setLayout(), instead only - fields belonging to the Form are copied.
    • -
- - -

Custom Tailored -Client-Side Components

- -

Due to the layout changes, all child component size changes -(outside the updateFromUIDL() function) must be announced. Most -commonly, this kind of change occurs when an image gets loaded inside a -component. There is a helper method componentSizeUpdated() in the -Util class for making the announcement:

- -
            Set<Widget> w = new HashSet<Widget>();
-            w.add(this);
-            Util.componentSizeUpdated(w);
-
- -

Themes

- -

Many components have changed significantly due to layout -refactoring. Especially the DOM structures of the components have -changed, which may break old themes.

- -

Building themes for Toolkit is not the most straightforward -process as there is quite a lot of JavaScript magic done while rendering -the components, e.g., dimension measuring, etc. If you use unsupported -CSS, a component may be rendered in an unexpected way in a browser. A -"Theme builder's Handbook" is at the top of our TODO list. In the mean -time, it is often safest to override the values defined in the default -theme.

- -

Especially, if you encounter problems with margins or spacings, -check the manual. Some CSS class names and conventions have changed as -well. (Many of the changes are not yet included in the manual.)

- -

If you have or get "broken" component on your screen, the first -thing to do is to comment out all your custom theme. If it works, you -may have the rework your CSS for that particular component. Below are a -few things to check:

- -
    - -
  • Do not use custom margins outside a component. In IT Mill - Toolkit, no component should have a margin defined. Settings - width/height on the server-side would mean offset width/height on - client-side, so using custom margins for components using CSS may break - some features in the layouts.
    • - -
  • The same goes for borders and paddings for the main element - unless they are used for the main element in the default theme. It is - often safer to use borders in the same elements that have borders in - the default theme or in inner elements.
    • - -
- -

The easiest and safest way to build a custom theme is, often, to -override the values from the default theme.

- -

Browser support changes -since 5.2.x

- -

Safari 2, Firefox 1.5, and versions of Opera prior to version 9.6 -are no longer supported. Users of these browsers are strongly encouraged -to upgrade to a newer version.

- -

Google Chrome is not yet supported, but it is known to work -rather well as it is a close relative to Safari.

- -

The GWT Hosted Mode Browser on Linux uses same Gecko version as -FF 1.5 and is currently partially broken. Some layouts do not render -properly. We hope to resolve these issues soon with next generation -Hosted Mode Browser aka OOPHM or with minor hacks to the client side -code.

- -

Miscellaneous Changes and Enhancements

- -

Version 5.3 also contains a large number (more than 200) of small -changes, which might not be worth mentioning in the release notes, but -below are some of them.

- -
    -
  • A new sub-window theme
    • -
  • The HTML structure of TabSheet has changed
    • -
  • Better shadow support for overlay elements
    • -
  • Row and column icons for Table
    • -
  • New component: PopupPanel/PopupView
    • -
  • Theme changing on-the-fly
    • -
  • Table cellstyle and rowstyle generators
    • -
  • New component: MenuBar
    • -
  • Security: double-cookie submission pattern
    • -
  • Low-level support for bookmarking and history
    • -
  • Sub-windows can be centered on screen. Modal windows are - centered automatically
    • -
  • The Link component now behaves like a normal "weblink"
    • -
- -

The release of IT Mill Toolkit includes new -features and a large number of fixes to problems compared to the older -5.2.x version. Major enhancements and dozens of bug fixes have been -implemented. Only the most significant issues are mentioned here.

- -

For up-to-date status of known problems, see the developer -website dev.itmill.com.

-

Package for the experimental GWT Out-of-Process Hosted Mode

We provide a separate (platform independent) installation package @@ -294,7 +56,7 @@ debugging purposes during development. For production use, you should compile your custom widget sets with the regular IT Mill Toolkit package for your platform.

-

Important known problems in

+

Important known problems in @version@