Note that this project is very new.

Booster is a RubyGem with support for writing rich client applications using Backbone.js and Handlebars.js. It integrates with the Rails Asset Pipeline in a somewhat peculiar way:

• Booster assets have the .boost extension and can optionally contain both JavaScript and Handlebars markup in the same file. Handlebars templates are compiled to JavaScript functions inline during processing. A TextMate bundle supporting both languages in the same file is included.
• Each processed asset is wrapped in a CommonJS-like API inspired by this Gist so that each asset essentially becomes a module closure that can be required by other modules.

In addition to the Asset Pipeline processor, Booster supplies a set of assets of its own that can be used in your applications. This includes support functionality on top of Backbone.js and Handlebars.js that you can choose to use or extend from rather than the stock Backbone types. This is explained in more detail below, and can be opted out.

Include the Booster gem in your Gemfile:

Gemfile:

group :assets do
  gem 'booster'
end

Require Booster in your application asset manifest which, in turn, will include Underscore.js, Backbone.js, and Handlebars.js (only the runtime part), on which Booster depends. You also need to require jQuery (supplied by Rails) before requiring Booster (or have it included on page from CDN before including Booster).

app/assets/javascript/application.js:

//= require jquery
//= require booster

The booster asset is the full package, including additional functionality for Backbone and Handlebars which you may not need. If you only need the core Booster functionality which includes module support and the Backbone and Handlebars dependencies, require the core asset instead:

app/assets/javascript/application.js:

//= require jquery
//= require booster-core

Also see the Wiki which contains more detailed information.

The app/assets/javascripts/views/user.js.boost asset below exports two Backbone views, Show and Edit, used for dealing with user models. In this example, both views are defined in the same module and the templates used by the views are defined in the same file, similar to what is possible in Sinatra

app/assets/javascripts/views/user.js.boost:

exports.Show = Backbone.View.extend({
  /* ... */

  render: function() {
    $(this.el).html(show(this.model));
  }

  /* ... */
});

exports.Edit = Backbone.View.extend({
  /* ... */
  
  render: function() {
    $(this.el).html(edit(this.model));
  }

  /* ... */
})

@@ show
  <h2>{{firstName}} {{lastName}}</h2>
  <pre>{{address}}</pre>
  ...

@@ edit
  <input name="firstName" value="{{firstName}}"/>
  <textarea name="firstName">{{address}}</textarea>

If templates are included in an asset they are to be placed at the bottom of the file. Each template is compiled to a JavaScript function with the same name as the @@ identifier and can be invoked directly from anywhere in the module as can be seen in the render() functions above.

To use this module, say from a router, you require it like a regular CommonJS module.

app/assets/javascripts/routers/user.js.boost:

var views = require('../models/user');

exports = Backbone.Router.extend({
  routes: {
    '/users/:id':      'show',
    '/users/:id/edit': 'edit'
  }

  show: function(id) {
    var view = new views.Show({
      model: /* load model */
    });
    /* add view to layout */
  },

  edit: function(id) {
    var view = new views.Edit({
      model: /* load model */
    });
    /* add view to layout */
  }
});

Booster includes some support functionality that we often use in our own applications. In most cases this comes in form of JavaScript mixins that you can use directly on your code as well as Handlebars helpers that you can use from your templates.

This support is included by default in the //= require booster directive described in Usage above. So if you required the full Booster bundle you are set. If you have //= require'd booster-core which does not include the extra support you can add the support on top of core:

app/assets/javascript/application.js:

//= require jquery
//= require booster-core
//= require booster-support

We might introduce additional Booster assets in the future which can be optionally required in the same way.

To be described. Currently not implemented.

We are working on a set of Rails 3 generators that can be used to speed up development. Using these generators you can create models, views, and routers, or complete scaffolds using the following commands:

> rails g booster:model Discussion
> rails g booster:view Discussion [index [show [edit]]]
> rails g booster:router Discussion
> rails g booster:scaffold Discussion

This will generate Booster modules for each type of artefact with a skeleton implementation to get you going quickly. It will also generate specs based on the Jasmine BDD library. This not only gives you a productivity boost but can also help establish a coding style in a project with many developers. To customize the templates used when creating the artefacts, just fork Booster on GitHub and edit the templates in lib/generators and include your updated Gem directly from GitHub in your Gemfile.