A new maintenance release of the framework is available.
qooxdoo 3.5.1 ships with around 90 bugfixes over the previous qooxdoo 3.5 release.
As a patch release qooxdoo 3.5.1 is fully backwards-compatible to the previous version. Nothing needs to be changed in your existing apps if they are already based on qooxdoo 3.5. When upgrading from an older version you can migrate directly to 3.5.1.
Download qooxdoo 3.5.1, checkout the detailed release notes and the manual.
Many thanks from the core developers to the community, particularly for reporting issues and your help in improving the framework.
Hi, we have been busy with quite a number of topics recently, often related to or around input-device independence, aka pointer event layer. As we are also working towards an upcoming qooxdoo 4.0 release, here is a longer list of framework tasks accomplished recently.
If you use the qooxdoo master version in your projects, please feel free to let us know about any issues you encounter, thanks.
Welcome. For a list of tasks accomplished during the last working week, use this bugzilla query.
Have a great weekend.
Welcome to a weekly status update.
Progress in pointer Branch
We’ve made good progress in the pointer branch and are very excited about the result. If you are curious, now it’s time for you to get started! Thanks in advance for your support.
Check out the pointer branch and build your app with it. If you have any error, make sure to read the preliminary release notes for qooxdoo 4.0, which holds more information on what API changed. Don’t worry about the long list of API changes. Only a few changes are to the public API (in the list the terms in bold). Your app would be affected if it uses this public API; you would have to adjust the terms in your code.
The majority of changes is to protected API, i.e. it could only affect you if you derived from framework classes (e.g. for creating custom widgets). Usually the renaming is straightforward, e.g. “Mouse” into “Pointer”, or “Click” into “Tap”. Of course, the qooxdoo migration job is going to list all (possible) names in your code that should be renamed.
Anyway, your existing and future qooxdoo apps will benefit from the input-device independence. The event API should also be quite consistent in terms of naming, so it’d be some pleasure to work with. Take the chance to get your feedback included before we merge the branch into master. The earlier the better, particularly well ahead before we ship the next release. Depending on your feedback and our own ongoing testing, we plan to merge the branch into master within a week’s span.
For a complete list of tasks accomplished during the last working week, use this bugzilla query.
Have a nice weekend.