Using Backbone.js models and collections with Qt and QML

Backbone QML TodoI have been a big fan of Backbone.js a long time. Together with Marionette.js it offers a solid toolkit to front-end web developers.

Lately I have worked with Qt and QML. With QML you can create nice user interfaces very easily, but what I have missed is that easy integration to backend applications. So I thought what if I try to use models and collections of backbone.js. I was quite a skeptical first, because backbone.js depends on jQuery with uses window and document objects that are not working in Qt. However I decided to try it.

Instead of jQuery, I grabbed Zepto.js that offers the same API as jQuery. I tuned the library slightly to get rid of errors related to window and document objects. There were not many of them.

Then I took underscore.js that backbone.js uses and finally backbone.js itself. I made slight changes to get them initialise correctly, but nothing big changes there.

After that I only needed to implement a simple application where I could test that everything is working. The result was much better than I expected. You can use directly Backbone’s collections and models with your Qt application and even listen events in your QML file, they just work.

Define backbone models and collections
// app.js
var baseUrl = "";
var Todo = Backbone.Model.extend({


var TodosCollection = Backbone.Collection.extend({
model: Todo,
url: baseUrl+”/objects/todos”,

parse: function(response) {
return response.results;

2. Use models and collections in QML file

function completeItem(index) {
var todo ={completed: true}, {
success: function(model) {
todoModel.setProperty(index, "itemProcessing", false);
error: function(){ console.log("error")}
} )
todoModel.set(index, todo);

3. Listen collection events in QML file

ListModel {
id: todoModel
Component.onCompleted: {
App.todos.on("add", function(todo) { todoModel.append(todo) });

So the first impact was very positive. I haven’t tested all functions of Backbone.js yet, so there may be some errors. However I don’t believe there are any fundamental errors that prevent using Backbone.js.

How to run Jasmine javascript tests in CI server (Ruby)

Jasmine.js is a great testing framework for Javascript. However running tests in Continuous Integration (CI) server is somehow problematic because the server usually does not have a screen where to open a browser.

The solution is to use Xvfb and headless gem:

Headless is the Ruby interface for Xvfb. It allows you to create a headless display straight from Ruby code, hiding some low-level action. It can also capture images and video from the virtual framebuffer.

To run your tests in CI server, do the following steps:

  1. Install xvfb
    $ sudo apt-get install xvfb
  2. Install firefox
    $ sudo apt-get install firefox
  3. Install headless gem
    $ gem install headless
    add it to Gemfile
    gem ‘headless’
    and run
    $ bundle install
  4. create rake task for headless jasmine runner (
  5. run or add rake task to your build configuration
    rake jasmine:ci:headless

How to implement TreeView with Backbone.js

I started to implement an application that uses backbone.js. One feature that I needed was some kind of treeview as a side menu. I searched some jQuery based treeviews (like jstree and jQuery plugin: Treeview) but they were not suitable as out of the box.

Finally I decided to implement feature by myself. I found that jstree had a very good model of <ul> and <li> element combinations and I went to that direction in my solution as well. See the DEMO

Basically I needed two Backbone View classes: TreeView and TreeViewItem.


TreeView class just creates the master <ul>-element (templates/treeview/menu.jst.ejs)

<ul id="menu"></ul>

The class also fetches root level collection of MenuItems and creates TreeViewItem for each item.


TreeViewItem has one MenuItem model and a collection of TreeViewItems. In the template (templates/treeview/item.jst.ejs) name of the item is displayed and <ul> element is rendered as sub menu placeholder.

<a href="#"><%= model.escape('name') %></a>

TreeViewItem handles clicks from arrow icon (<ins>-element has arrow image as a background) and opens/closes sub menu.

Both views extends Support.CompositeView (from backbone-support library).


application.js contains required libraries
backbone_treeview.js initializes TreeView class

window.BackboneTreeView = {
    Models: {},
    Collections: {},
    Views: {},

    menu: null,

    initialize: function() {


    initializeMenu: function() { = new BackboneTreeView.Views.TreeView();;


$(document).ready(function() {


How would you improve the implementation and should I make it as a library?

Link to project source:

My favourite Prototype and Scriptaculous plugins

The unpleasant fact is that Prototype JavaScript framework is dead or at least dying. JQuery is nowadays a de facto JavaScript library and almost all the great tools are designed to use with JQuery (Bootstrap, from Twitter etc).

However there are still lots of people using Prototype or at least would be willing to use it with UI libraries by Scriptaculous and do some awesome stuff. In some level I still prefer Prototype and Scriptaculous to JQuery. Jarvis Badgley has summed this issue very good in his blog post.

If you are stuck with Prototype and Scriptaculous, there are still great and working plugins that extend Prototype and Scriptaculous. I will list now three plugins that I have lately found helpful.

Image gallery & Slideshow

Tom Doyle initially developed Simple image gallery and slideshow and Dave from ISOTOPE Communication has improved the script.


Carousel is a highly configurable Prototype extension that creates a nice way of presenting content that is logically broken into several pieces / steps / etc


Accordion by Kevin Miller is a lightweight accordion that supports both vertical and horizontal accordions.

Do you use still Prototype and Scriptaculous? Have you any hints or recommendations about great plugins?