for QWT 0.2.0.

QWT is early beta, it needs much more testing.

• QWT has its own versioning scheme now.
  The previous release was 0.7.2, reflecting the associated qooxdoo version. Starting with this release QWT 0.2.0 the version number reflects QWT's own development status independent of the qooxdoo version used.
• Simplified setup
• Microsoft Windows support in addition to Linux and Mac OS X
• Every application has a client.Main and a server.Main now
• Service objects renewed to support Reverse Ajax
  Please refer to the documentation and remember to rename you interfaces FooServices to FooService when upgrading.
• Switched to Tomcat 6.0.14
• Provided Target.addJavaEventListener to listen for arbitrary events
• Directory target/webapp/main was renamed to target/webapp/client
• The module server was renamed to engine

QWT's compiler translates Java to JavaScript. It support all Java 5 language features except

• byte, long, float, double
• … arguments
• autoboxing
• non-static member classes

QWT includes a JavaScript version of the Java standard class library, providing a subset of Java SE 5 standard classes from java.lang and java.util. Not supported are files, networking, AWT and Swing.

For more details see the source code.

QWT provides binding classes for all Qooxdoo classes. A binding class is a Java class with the same API as the respective JavaScript class.

Limitations:

• binding classes have no static methods.
• binding classes do not inherit java.lang.Object. Thus, they do not have standard methods like getClass() and hashCode().

A simple serialization mechanism is used to pass objects by value between client and server. This mechanism supports

• trees only, no graphs
• no inheritance
• no arrays

All client-server communication is synchronous.

When running on the server, proxy objects may not return values because clients cannot currently pass results back to the server.

A class cannot implement more than one service interfaces.

QWT should support every browser supported by qooxdoo. However, client-server communation does not use qooxdoo, so this is a place where cross-browser problems might creep in. Firefox got most testing, followed by Safari 3 and IE 7.

Applications crash in IE 6 and Opera.

Most browsers limit the number of simultaneous XmlHttpRequest to 2. They want to restrict resource consumption imposed by arbitrary web sites.

As a result, you can start only one Chat application at a time, you can not open a new window or a new tab with a second chat user. To work with two char users, you need two different browers (e.g. IE and Firefox). Alternatively, you can re-configure your browser to allow more than 2 simultaneous XmlHttpRequests.

(More details for Firefox.).

QWT applications needs at least 2 simultaneous XmlHttpRequest. The Hello application doesn't load images if you allow only 1 request.

Restarting a QWT application with active clients may crash the server if an old client sends requests to a new server.