Table of Contents

qooxdoo 4.0 (2014-06-05)

Summary

This release comes with exciting new features besides a large number of bugfixes.

Also checkout the release announcement in the blog.

Bugfixes

See the corresponding bugzilla query for the issues resolved for qooxdoo 4.0.

Sections

To quickly jump to a certain section (all sections are listed alphabetically below) use the following links:

app

app.apiviewer.desktop

app.apiviewer.website

app.demobrowser

app.featureconfeditor

app.feedreader

app.mobileshowcase

app.playground

app.showcase.desktop

app.testrunner

app.testrunner.website

app.todo

app.tutorial

app.widgetbrowser.desktop

app.widgetbrowser.website

core

core.application

core.databinding

core.dev

core.dev.testing

core.event

core.io

core.io.part

core.io.remote

core.locale

desktop

desktop.bars

desktop.form

desktop.list

desktop.table

desktop.theming

desktop.tree

desktop.virtual

documentation

documentation.api

documentation.manual

mobile

mobile.core

mobile.layout

mobile.theming

mobile.widget

tool

tool.generator

tool.generator.compiler

tool.generator.config

tool.grunt

tool.test.automation

website

website.animation

website.bom

website.dom

website.modules

website.widgets

Migration

API Changes

Pointer support

The following section contains the list of API that changed for input-device inpendendence, aka "pointer" support.

Many of the fundamental changes could be addressed by a simple renaming scheme. Think along those lines:

Besides this basic pattern, the actual changes are given explicitly by the list below. Public methods are bold and as such regular app code could be affected. Protected methods start with an underscore and should only be relevant if you derived from the corresponding class. Thus if you didn't use protected methods in your code, you can simply focus on the few public API changes.

Some other changes related to pointer support that you might want to look into:

Other Changes

qx.bom.Attribute has been changed for boolean attributes. Setting a boolean attribute to an empty string does not remove the property anymore. This behavior is aligned to the native getAttribute behavior. See bug 8240 for more defails.

Missing Features