The qooxdoo Web Toolkit has been created and is maintained by Michael Hartmeier (mlhartme AT users DOT sourceforge DOT net) in close cooperation with the qooxdoo core developers. It is still at an early stage and not recommended yet for production.

All interested people are invited to be part of this open source project. Please use the regular qooxdoo mailing list for feedback and discussion.

A QWT application consists of a client and server part, both written in Java. QWT translates the client part to JavaScript to be executed in the browser; the server part runs in a servlet container. With this approach, Java programmers can easily leverage the power and tool chain of their favorite language to create impressive, cross-browser web applications - without any knowledge of JavaScript, HTML, CSS or DOM.

• QWT for Java Programmers
• QWT for qooxdoo Programmers
• Similar Projects

QWT is a regular contribution to the qooxdoo framework. Please use the normal qooxdoo mailing list for QWT discussion.

• Java-to JavaScript Compiler
• all qooxdoo classes available in Java
• RMI-style client server communication
  • applications simply invoke methods, networking and Java/JavaScript switching is handled transparently
  • uses Reverse Ajax to implement client-to-server calls
• Maven build system

QWT is covered by the same LGPL/EPL dual license as qooxdoo: It may be used under the terms of either the

• GNU Lesser General Public License (LGPL)

or the

• Eclipse Public License (EPL)

As a recipient of QWT, you may choose which license to receive the code under.

I started QWT as my pet project because I was fascinated by RIAs: A qooxdoo application was completely different from what I knew before. However, it was JavaScript, which is not particularly well suited for larger applications … I'm a Java guy. I played with several ways to combine Qooxdoo with Java, but didn't find a convincing solution – until Google releases GWT. They didn't initially release the source code, so I picked their idea and continued in this direction. When Google releases the source code, I almost had a running example, so I continue to get it out the door.

We decided to Open-Source QWT because it's too big for me alone, and I had less and less time to work on it. In June last year, the project stalled since I took a 4 month vacation. After that, I continued on other projects. My company targeted qooxdoo primarily for Web Developers, who are not attracted by writing Java Code, they prefer JavaScript.