Here you will be able to find answers to questions from users that have been asked previously. If your question is not answered here, please be sure to check our current qooxdoo documentation and the mailing list for more help.

For the peace of mind of our english speaking friends: It’s like “cooks-do”, as in the sentence “Cooks do cooking for their living”.

Starting with release 0.6.5 qooxdoo is dual-licensed under the GNU Lesser General Public License (LGPL) and the Eclipse Public License (EPL). Version 0.6.4 and below are licensed solely under the LGPL. For a full understanding of your rights and obligations, please consult qooxdoo’s licensing information.

You can edit this Wiki. See here for more information.

qooxdoo supports most current browsers. For a detailed overview follow this link to our documentation pages.

Please note though, that when working with qooxdoo, you don’t need to detect or work around issues in the client’s browser. qooxdoo goes to great length, abstracting browser specifics, thus freeing the developer from tedious cross-browser issues.

There is a download page with links to the distribution and further information.

Have you used a filename other than “Application.js” for your main application class? If so, you will have to add the following entry in your makefile, using an appropriate value for “MyApplication”

APPLICATION_CLASSNAME = $(APPLICATION_NAMESPACE).MyApplication

There is a tool that is part of the development tool chain to extract your Javadoc-like source code comments and view them in an auto-generated API Viewer.

There is some qooxdoo-specific support in the Aptana IDE. JSEclipse has limited support for qooxdoo 0.5.x.

This depends on two factors:

• The time it takes for a user to download the files: A user’s internet connection and overall ability to transmit information will make the first impact on qooxdoo’s load time.
• The speed of a user’s computer: Once downloaded, qooxdoo must be loaded by the web browser and initialized. Like all JavaScript based applications this process can be quite CPU intensive.

If you use Firefox, make sure the option Preferences → Content → Enable Javascript → Advanced → Disable or replace context menus is checked, so that context menus are not hidden by the browsers default context menu.

This is because of the security-settings of the browser. In IE you can add the site to the trusted sites. After doing this, the statusbar is gone.

SP2 introduced a new ActiveX setting, that may cause your IE to not display PNGs: if “Binary and script behaviors” in your browser settings is disabled, QxImage will not be able to show any PNG. It simply keeps displaying an invisible blank.gif that is preloaded to fix the well-known alpha transparency bug in IE6 or below. Please make sure you enabled this setting.

• Manual
• Overview of framework features
• API Viewer
• Online demos, particularly the Demo browser
• User-provided code snippets
• Community
• Mailing list