qooxdoo-contrib 3.0

For many years now an infrastructure for user-provided contributions to the qooxdoo framework has been available. As most of you certainly know, it goes by the name of “qooxdoo-contrib“.

While sticking to the very name, it has seen many significant changes over time. For instance, from its initial SVN repo at Sourceforge; over its deep (but often problematic) integration into the framework’s toolchain; all the way to a semi-dynamic, web-based catalog. Nevertheless it (mostly) kept moving into the right direction, trying to make it easier to collect, manage and use contributions to qooxdoo.

Just recently qooxdoo-contrib has been brought into a fairly decent state, allowing for easier participation. Much feedback from users and contributors has been incorporated into its fundamental overhaul.

To test-drive the new infrastructure, we invited Norbert Schröder for his recent theme contributions. He successfully managed to add, modify and publish the following three themes – all by himself:


The former qooxdoo-contrib has now been switched to the new infrastructure. That doesn’t mean qooxdoo-contrib is “done”. There are still some tasks to get rid of the old infrastructure entirely.

Moreover, qooxdoo-contrib might even look quite different in the future. Not just in terms of a nicer presentation, maybe also in its technical base for managing user-contributed packages. But that also depends on you. Because its further evolution (in terms of appearance, content, infrastructure) can now – for the first time – be handled according to the need and engagement of the community. The infrastructure of qooxdoo-contrib has therefore been made self-contained, transparently being hosted at Github, allowing but also requesting interested people to engage in improving it.

The current state of qooxdoo-contrib may be just an intermediate milestone, but a good starting point for the community to further improve it. For instance, to streamline it, to make it fool-proof, to automate it. Get familiar with the current infrastructure and the procedures, check out its concise documentation at Github. Pull requests welcome. Feel free to use the qooxdoo-devel mailing list for discussions.

On a side note, the work on the new qooxdoo-contrib, built upon a transparent Github infrastructure for easier management and collaboration, was also to evaluate to move other parts of the qooxdoo project over to Github. I.e. not only leveraging Git repos, but gh-pages or wiki (instead of the Dokuwiki-based homepage), issue tracking (instead of Bugzilla), etc. Some of the project’s proprietary infrastructure just needs to be replaced by more manageable solutions, open for participation. While this is still work in progress and under evaluation, it’s certainly the way to go to allow for easier management and collaboration of the qooxdoo project in general. Stay tuned.

qooxdoo 5.0.1 released

A new maintenance release of the framework is available.

qooxdoo 5.0.1 ships with a few bugfixes over the previous qooxdoo 5.0 release. It particularly improves support for Microsoft Edge, the new browser of Windows 10, which was finally released after qooxdoo 5.0.

As a patch release qooxdoo 5.0.1 is fully backwards-compatible to the previous 5.0 version. Nothing needs to be changed in your existing apps if they are based on 5.0.

Even for apps based on qooxdoo 4.1.x updating should be rather trivial; just consult the previous release info. When upgrading from an older version, use migration support to get directly to 5.0.1.

Download qooxdoo 5.0.1. Check out the release notes and the manual.

Many thanks to the community for reporting issues and your support in improving the framework.

The week in qooxdoo (2015-09-11)

Welcome back to a brief status update.

See a list of tasks accomplished recently. Thanks for any detailed bug reports or even pull requests provided.

Upcoming Release

qooxdoo’s previous releases already came with preliminary support for the preview versions of Windows 10 and its new “Edge” web browser. Both of those Microsoft technologies shipped in their final version a few weeks ago. Indeed, some issues were found, but they could already be addressed in the framework code base.

Therefore we plan to ship a maintenance release qooxdoo 5.0.1 with improved Win10/MSEdge support by the end of next week. In the mean time, if you encounter issues with the latest devel version of qooxdoo, please file bug reports asap, thanks.

C U.

Real-life Example: Bibliograph

This is to let you know about a user-contributed example of a qooxdoo app in production, on behalf of its creator Christian Boulanger. Thanks Christian for the input, and good to see you keep enjoying and successfully leveraging qooxdoo!

Bibliograph is a powerful open source web application for the collaborative collection, editing and publishing of bibliographic data.



if you are interested in qooxdoo apps “in the wild”, Bibliograph v2.1 has just been released. It is based on qooxdoo 4.x (next version will upgrade to qooxdoo 5.x). A live preview is at http://demo.bibliograph.org .

For what it’s worth, the current version uses “qooxdoo parts” to implement an on-demand plugin system (as I was told, this was NOT the part system’s intended use case, but it works nonetheless).

More information is on http://www.bibliograph.org .

The app has been based on qooxdoo since version 0.5 and I have not regretted this a single day. Upgrades have been mostly painless. qooxdoo FTW!