The week in qooxdoo (2010-05-28)

Welcome back to another weekly status update.

Manual goes SVN

We’ve decided to move the manual out of the wiki and into SVN. People working with trunk might have already noticed the new top-level documentation file tree. The benefits for this move include:

  • keep the manual in close sync with the release cycles of the framework
  • providing an offline version, alongside with the online version, that can e.g. be shipped with the SDK
  • providing a PDF version, e.g. for download
  • better editor support than what the wiki software can provide in the browser
  • document management functions, like automatically generated TOC, indexes, etc.

So starting with qooxdoo 1.2, we will maintain the manual pages in SVN and will be putting static HTML pages online. It is expected to fit these manual nicely into the existing homepage structure and design just like the existing wiki-based manual. The new manual will also come with a full-text search facility. The HTML pages are generated from the text files in the repository. The markup for these text files will be reStructured Text, the current choice for the documentation system to create the various output formats is Sphinx. Just like the qooxdoo toolchain, Sphinx is also Python-based and runs cross-platform. The wiki-based homepage with all its non-manual pages will stay as it is, however it is planned to update the underlying Dokuwiki to a current version as well. There will be some more announcements relating to that topic in the weeks ahead, so stay tuned.

Bugfixes

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

qooxdoo + Lisp = qooxlisp

Kenny Tilton let us know this week that he released “qooxlisp“, a new Lisp-based RIA framework under MIT license:

“What is qooxlisp? In brief, we drive a kick-ass Javascript RIA Web application framework from a Lisp application running on the server, managing in the end to turn a thick client into a slave programmed wholly from a server-side application.

Benefits

  • The Grand Re-Unification of application code, with everything on the server side, including the code that has to run on the client-side. Thank you, content-type “text/javascript” and eval.
  • All the power of a big programming language and all the libraries it can reach. Javascript is neat (and Lispy!) but just a toy.
  • All the power specifically of Common Lisp. You have no idea, but this might help. And I do not even mention macros!
  • The performance of a natively compiled language. Yes, Virginia, many Common Lisp implementations compile natively.

Ingredients

  • qooxdoo: a great Web application development framework.
  • Lisp: the only way to program.
  • Cells: dataflow aka functional reactive programming aka constraints. The only thing better than Lisp. Fans of OpenLaszlo, FrTime, Python Trellis, or qooxdoo’s own databinding scheme will understand. Basically, one gets a declarative programming paradigm in which data dependencies are established transparently and arbitrary invariants enforced automatically, as if one were using a spreadsheet such as VisiCalc or Lotus 1-2-3.

For more info see here.”

That’s it for today. C U around next week.

One thought on “The week in qooxdoo (2010-05-28)

  1. > Just like the qooxdoo toolchain, Sphinx is also Python-based and runs cross-platform.

    To forestall misunderstandings: qooxdoo users will *not* have to deal with Sphinx. It’s just one of the behind-the-scenes tools that are part of our project infrastructure, supporting our publishing and release activities. Its mentioning here is merely informational.