The week in qooxdoo (2013-03-01)

Welcome to the weekly status update.

qx.Website: Improved Code Examples

We’ve added numerous code examples to the qx.Website component’s API Viewer. Many of them are self-contained, and their HTML and CSS as well as JavaScript code can be executed and edited on jsFiddle with the click of a button.

Lint Warnings

The built-in system for code validation has seen some overhaul. For one thing, lint warnings are now issued with every run of a build job (like ‘source’, ‘build’, etc.). So far, the warnings would only be shown once and then disappear although the issue might persist. Only when the class was touched and then parsed again would the lint warnings re-appear, which could be confusing.

But you can also turn off lint-checking when running build jobs, so it’s no longer mandatory. While the lint checking during compilation is moderate and less picky than running the explicit ‘lint’ job, it incurs a bit of a runtime penalty that you might want to avoid in certain situations. The corresponding config key is compile-options/code/lint-check, which is also exposed by a new config macro, COMPILE_WITH_LINT. But this key is still true by default.

Furthermore, the check set of classes to match a global symbol found in code against has been changed. So far, it was the set of all class defined in all involved libraries. For the ‘lint’ Generator job, this is still the case. But for compile jobs, this has been changed to only consider classes in the current build. I.e. only a class that is actually included in the current build will be considered “known” when lint-checking symbols.


For a complete list of tasks accomplished during the last working week, use this bugzilla query.

That’s it for now, see you next week.