qooxdoo, re-shaped

When you read this qooxdoo has gotten a new face.  We changed the project’s visual theme, new colors, new fonts, new icons, new layouts. You will still find your way round, though: The home page wiki, the blog, the manual, the demos, the issue tracker.

But it’s not just a face-lift.  The visual change also signals a shift in conceptual focus and orientation. We want to open qooxdoo up, break it down, and re-arrange it for a new phase. All the traditional elements of a GUI framework for desktop-like applications in the browser are still there, with qooxdoo “Desktop“, and will continue to be. But many parts that were previously subsumed in this single dedication are now being brought to light and exposed, so they can be used individually and independently.

One obvious of those parts is the mobile endeavor. Mobile is big time, and with all the potential hype stripped off there is still a stunning growth of devices. And with that there will be a substantial need for mobile apps. And a substantial share of those apps will run on the web platform, HTML, CSS, JavaScript. So many of you will not have been surprised that qooxdoo increasingly picked up mobile topics over the last 12 or so months. Now we want to address and exhibit the mobile topic in a prominent way, with qooxdoo “Mobile“.

Another part that is lifted to first-class membership and prominence is the low-level, GUI-free layer. It has always been there, but it was not easily accessible. The new “Website” component of qooxdoo changes this, and it’s not just a collection of relevant qooxdoo classes. It has a completely new interface, terse, procedural,  familiar that caters for the programming needs of  developers that build web pages without widgets. A single-file download and you’re ready to go.

The final part, which you saw us making first steps with some time ago, is the “Server” component. This is DOM-less, and allows developers to use qooxdoo entirely outside the browser context. It is no news that JavaScript has spread all across the IT stack, and is usable on increasingly diverse platforms, Node.js probably being the most popular today. Those developers will deploy qooxdoo for its class system, the interfaces, mixins, properties and custom events, as a sane way to develop large and scalable JavaScript applications that run as servers and clients, command line tools and scripts.

So here we are. It looks new, and has a new story. Plenty of opportunities ahead. Let’s get it on.

16 thoughts on “qooxdoo, re-shaped

  1. The new website looks clean, focussed and attractive. Very good job. It was also a very good idea to split up the library in components (and to add databinding to the server library!)

  2. Very nice work, guys, congrats !

    Where can I download the desktop version ? On the download page, I’m only able to see the 1.6…

    Thanks again for your amazing work.

  3. I like the new look. We needed such a change. However, consider that you might have some broken links inside. I think I have found some.

    Good luck!

  4. @LoremIpsum Thanks. As for the downloads, we used to only feature released versions so far. Only now we weakened that as we don’t have released packages for all components (like Website). 1.6 is the latest release. Do you think there is demand for a ‘devel’ SDK download?

    @Marius Broken links: Yes, definitely. If you find some, please pass them on to us.

  5. @Thomas Herchenröder : I don’t fully understand the different versions, what exactly do you call the 2.0 ? Actually I was expecting some kind of qooxdoo-2.0-sdk.zip download, but my major demand would be on the Indigo theme :-)

    Thanks again

  6. @LoremIpsum (a) 2.0 is the version of the upcoming, not yet released qooxdoo version. It is developed as ‘devel’. 1.6 is ‘current’, and 1.5.1 is ‘maintenance’. (b) There is no ‘devel’ SDK to download, as I wrote before. Not sure if we should offer one. (c) Indigo will be available with the 2.0 release. Until then, you have to get a Git checkout (or zip ball download) to use it.

  7. @Thomas Herchenröder : allright, I understand now ^^

    Well then maybe a ‘devel’ version of the SDK could be interesting, yes, it could be kindo of a beta version. I would download it, as far as I’m concerned.

  8. Pingback: The week in qooxdoo (2012-04-20) | qooxdoo News

  9. Hey @Thomas, Good nice website! Our website is very clean and amazing :) . I like this.. If your next new version of framework / SDK comes 2.0 and sdk will come and release again?

    What are feartures different? server, desktop and website? Can i use code without sdk? Or i must need sdk? Good job for sweet amazing freamework :)

    Best regards Jens

  10. @Jens Thanks! I’m not sure what you mean regarding our next release, but yes, the release 2.0 will bring a new SDK with the latest framework classes.

    Concerning the different components: Desktop encompasses the “classical” SDK for browser GUI development, so requires the SDK to work with. Website is for low-level browser development (jQuery/Prototype level) and is available as .js download, no SDK required. The same is true for Server, which contains even less classes as it doesn’t address the DOM, just the class sytem, properties, custom events, simple data-binding.

  11. @Thomas, ok i understand. Good luck for release of our qooxdoo :) . And can Qooxdoo work completed desktop applications? Does Qooxdoo work under Adobe Air 3.3 and Titanium Studio 2 ?

  12. @Jens It really depends. We haven’t tested Air for along time, as it prevents our basic model of loading additional script files during run time. The mobile Feedreader has been deployed as a Titanium app recently with success, but the mobile GUI is limited by nature. So I think it really depends on which qooxdoo features you are using. It might not be far off supporting the entire Desktop scope on both platforms, but we don’t actively pursue this at the moment.

  13. Pingback: qooxdoo 2.0 released | qooxdoo News