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 <version> and <platform> tags in some HTML and text files to @...@ notation to avoid some validation errors in Eclipse.


svn changeset:7352/svn branch:6.0

2 files changed, 4 insertions, 242 deletions

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 @@
 				<div class="top"></div>
 				
 				<h3>&raquo; Package contents</h3>
-				<em>Version <version></version></em>
+				<em>Version @version@</em>
 				
 				<div id="package-contents-content"> <!-- For JavaScript hooking -->
 				
 				<div class="library">
 					<h5>Library</h5>
 					<p>Contains all you need to start a new Toolkit project (binaries, sources, default 
-					themes and widgetsets). <a href="itmill-toolkit-<version></version>.jar">Toolkit JAR</a></p>
+					themes and widgetsets). <a href="itmill-toolkit-@version@.jar">Toolkit JAR</a></p>
 				</div>
 				
 				<div class="documentation">
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</a></div>
 <div class="content">
 
 <div>
-<h2>Release Notes for IT Mill Toolkit Version <version></version></h2>
+<h2>Release Notes for IT Mill Toolkit Version @version@</h2>
 
 <p>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.</p>
 
-<h2 id="ClientsideiscompiledwithGWT1.5">Google Web Toolkit Upgraded
-to Version 1.5</h2>
-
-<p>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 <a class="ext-link"
-	href="http://code.google.com/webtoolkit/"><span class="icon">GWT
-web site</span></a>.</p>
-
-<h2 id="Java5isrequired">Java 5 Now Required</h2>
-
-<p>As GWT now requires Java 5, support for Java 1.4 is discontinued
-also in IT Mill Toolkit.</p>
-
-<p>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.</p>
-
-<h2>Debug Mode Enabled by Default</h2>
-
-<p>The debug mode is now enabled by default, to allow debugging
-layout and other problems more easily. The debug mode:</p>
-
-<ul>
-	<li>Displays debug data to the server console/log.</li>
-
-	<li>Allows showing the client-side logging window, which you can
-	enable by adding the request parameter "<tt>?debug=true</tt>" to the
-	application URI.</li>
-
-	<li>"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 <tt>System.out</tt>.</li>
-</ul>
-
-<p>You should disable the debug mode when releasing your application
-for production use. You can do this by including the following setting
-in your <tt>web.xml</tt>.</p>
-
-<pre class="wiki">  &lt;context-param&gt;
-  	&lt;param-name&gt;productionMode&lt;/param-name&gt;
-  	&lt;param-value&gt;true&lt;/param-value&gt;
-  	&lt;description&gt;IT Mill Toolkit production mode&lt;/description&gt;
-  &lt;/context-param&gt;
-</pre>
-
-<h2 id="Layoutchanges">Layout Changes</h2>
-
-<p>The stable IT Mill Toolkit version 5.3 introduces a major rework
-of layout components since the beta versions 5.2.x and before.</p>
-
-<p>Major changes include:</p>
-
-<ul>
-	<li>Layouts are stricter than before - <i>usage of debug mode
-	during development is recommended. Use "Analyze layouts" in client side
-	debug window if you encounter problems with relative size.</i></li>
-	<li><b>VerticalLayout</b> and <b>HorizontalLayout</b> obsolete <b>
-	<s>OrderedLayout</s></b></li>
-    <li>Layout cell alignment has changed</li>
-	<li><b><s>ExpandLayout</s></b> deprecated</li>
-	<li>Default sizes have changed</li>
-</ul>
-
-<h3>OrderedLayout deprecated</h3>
-
-<p><b>VerticalLayout</b> and <b>HorizontalLayout</b> replace the old
-<b><s>OrderedLayout</s></b>, which is now deprecated.</p>
-
-<p>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 <tt>setOrientation()</tt>
-any longer, though such need is rare anyhow.</p>
-
-<h3>Layout Cell Alignment Changed</h3>
-
-<p>Previously, the alignment of components within layout cells was set with
-<i>setComponentAlignment()</i> with constants for <b><s>OrderedLayout</s></b> (now
-<b>VerticalLayout</b> and <b>HorizontalLayout</b>) and <b>GridLayout</b> separately, such
-as <tt>OrderedLayout.ALIGNMENT_TOP_LEFT</tt>. Now the method takes constants defined in
-<b>Alignment</b>.</p>
-
-<p>For example, aligning a component "top left" is now:</p>
-
-<pre>mylayout.setComponentAlignment(mycomponent, Alignment.TOP_LEFT);</pre>
-
-<p>You can also give an <b>Alignment</b> object as a parameter and give horizontal and
-vertical alignment separately with bitmask parameters.</p>
-
-<h3 id="HandlingofrelativesizeshavechangedExpandLayoutdeprecated">Handling
-of relative sizes has changed, ExpandLayout deprecated</h3>
-
-<p><b><s>ExpandLayout</s></b> is deprecated. You can now define the
-relative sizes of components more flexibly with <tt>setExpandRatio()</tt>
-method available in <b>VerticalLayout</b> or <b>HorizontalLayout</b>.</p>
-
-<p>See the article on <a class="wiki"
-	href="http://dev.itmill.com/wiki/DevDocs/RFC/RelativeSizes">Relative
-sizes in IT Mill Toolkit</a> for details.</p>
-
-<h3 id="Somecomponentsnowhavedefaultsizes">Some components now have
-default sizes</h3>
-
-<p>Previously, almost all components had undefined size by default.
-Now some containers have 100% width by default. These components are:</p>
-
-<ul>
-	<li><b>VerticalLayout</b></li>
-	<li><b>Window</b></li>
-	<li><b>Panel</b></li>
-	<li><b>TabSheet</b></li>
-	<li><b>SplitPanel</b> (note that <b>SplitPanel</b> also has 100%
-	height by default)</li>
-	<li><b>Form</b></li>
-	<li><b>FormLayout</b></li>
-	<li><b>Label</b></li>
-</ul>
-
-<p>If the width of a <b>Label</b> 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.</p>
-
-<h3>Miscellaneous Layout Changes</h3>
-
-<ul>
-	<li>You can now give component alignments inside layouts easily
-	with <tt>setComponentAlignment()</tt> as a string, such as "<tt>top
-	left</tt>" or "<tt>m,c</tt>" (for middle-center). See <a
-		href="http://dev.itmill.com/ticket/2279">#2279</a>.</li>
-
-	<li><b>Form</b> no longer copies all components from the old
-	layout to the new one when doing <tt>setLayout()</tt>, instead only
-	fields belonging to the <b>Form</b> are copied.</li>
-</ul>
-
-
-<h2 id="Customtailoredclientsidecomponents">Custom Tailored
-Client-Side Components</h2>
-
-<p>Due to the layout changes, all child component size changes
-(outside the <i>updateFromUIDL()</i> function) must be announced. Most
-commonly, this kind of change occurs when an image gets loaded inside a
-component. There is a helper method <i>componentSizeUpdated()</i> in the
-<b><i>Util</i></b> class for making the announcement:</p>
-
-<pre class="wiki">            Set&lt;Widget&gt; w = new HashSet&lt;Widget&gt;();
-            w.add(this);
-            Util.componentSizeUpdated(w);
-</pre>
-
-<h2 id="Themes">Themes</h2>
-
-<p>Many components have changed significantly due to layout
-refactoring. Especially the DOM structures of the components have
-changed, which may break old themes.</p>
-
-<p>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.</p>
-
-<p>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.)</p>
-
-<p>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:</p>
-
-<ul>
-
-	<li>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.</li>
-
-	<li>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.</li>
-
-</ul>
-
-<p>The easiest and safest way to build a custom theme is, often, to
-override the values from the default theme.</p>
-
-<h2 id="Browsersupportchangessince5.2.x">Browser support changes
-since 5.2.x</h2>
-
-<p>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.</p>
-
-<p>Google Chrome is not yet supported, but it is known to work
-rather well as it is a close relative to Safari.</p>
-
-<p>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.</p>
-
-<h2 id="MinorChanges">Miscellaneous Changes and Enhancements</h2>
-
-<p>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.</p>
-
-<ul>
-	<li>A new sub-window theme</li>
-	<li>The HTML structure of <b>TabSheet</b> has changed</li>
-	<li>Better shadow support for overlay elements</li>
-	<li>Row and column icons for <b>Table</b></li>
-	<li>New component: <b>PopupPanel</b>/<B>PopupView</b></li>
-	<li>Theme changing on-the-fly</li>
-	<li><b>Table</b> cellstyle and rowstyle generators</li>
-	<li>New component: <b>MenuBar</b></li>
-	<li>Security: double-cookie submission pattern</li>
-	<li>Low-level support for bookmarking and history</li>
-	<li>Sub-windows can be centered on screen. Modal windows are
-	centered automatically</li>
-	<li>The <b>Link</b> component now behaves like a normal "weblink"</li>
-</ul>
-
-<p>The <version></version> 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.</p>
-
-<p>For up-to-date status of known problems, see the developer
-website <a href="http://dev.itmill.com/">dev.itmill.com</a>.</p>
-
 <h2>Package for the experimental GWT Out-of-Process Hosted Mode</h2>
 
 <p>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.</p>
 
-<h2>Important known problems in <version></version></h2>
+<h2>Important known problems in @version@</h2>
 
 <ul>
 	<li><a href="http://dev.itmill.com/ticket/1155">#1155</a>