Introduction To Version 2.0, Modern Edition.

When I wrote the original Backbone Store, I didn’t have a clear understanding of how Backbone worked.  I wrote it to teach myself Backbone, after all.  Since then, I’ve come to understand that there is some Javascript about which I didn’t have the world’s clearest understanding.  This version of the store clears up those misconceptions and illustrates a clear separation between the data layer and the presentation layer.  Because of this clarity, it looks much less like the original JSON store tutorial for Sammy.js.

This particular document shows my current work kit.  I have provided a version of The Backbone Store 2.0 for main-line coders who still use Javascript, HTML and CSS with Backbone, but after doing so I decided to re-write all of my code to show how I really work, with Coffeescript, HAML, Stylus, and Backbone.  This is the result.

CoffeeScript is a lovely little languange that compiles into Javascript. It provides a class-based architecture (that is compatible with Backbone), has an elegant structure for defining functions and methods, and strips out as much extraneous punctuation as possible. Some people find the whitespace-as-semantics a'la Python offputting, but most disciplined developers already indent appropriately and find using Coffeescript a breeze.

HAML is a languange that compiles into HTML. Like CoffeeScript, it uses whitespace for semantics: indentation levels correspond to HTML containerizations. It allows you to use rich scripting while preventing heirarchy misplacement mistakes. Its shorthand also makes writing HTML much faster.

Stylus is languange that compiles into CSS. Like CoffeeScript and HAML, it uses whitespace for semantics.  (If you're detecting a theme here, you should know by now that I'm a Python partisan.)  It also provides mixins and functions that allow you to define visual styles such as borders and gradients, and mix them into specific selectors in the CSS rather than having to write them into the HTML.

Backbone.js is a popular Model-View-Controller (MVC) library that provides a framework for creating data-rich, single-page web applications. It provides (1) a two-layer scheme for separating data from presentation, (2) a means of automatically synchronizing data with a server in a RESTful manner, and (3) a mechanism for making some views bookmarkable and navigable.

There are a number of other good tutorials for Backbone (See: Meta Cloud, &Yet's Tutorial, Backbone Mobile (which is written in Coffee), and Backbone and Django. However, a couple of months ago I was attempting to learn Sammy.js, a library very similar to Backbone, and they had a nifty tutorial called The JsonStore.

In the spirit of The JSON Store, I present The Backbone Store, Modern Edition.

Literate Program

A note: this article was written with the Literate Programming toolkit Noweb. Where you see something that looks like <>, it's a placeholder for code described elsewhere in the document. Placeholders with an equal sign at the end of them indicate the place where that code is defined. The link (U->) indicates that the code you're seeing is used later in the document, and (<-U) indicates it was used earlier but is being defined here.


This is version 2.0 of The Backbone Store. It includes changes to the store based upon a better understanding of what Backbone.js can do. This version uses jQuery 1.6.2 and Backbone 0.5.2.

The Store

To demonstrate the basics of Backbone, I'm going to create a simple one-page application, a store for record albums, with two unique views: a list of all products and a product detail view. I will also put a shopping cart widget on the page that shows the user how many products he or she has dropped into the cart. I'll use jQuery's fadeIn() and fadeOut() features to transition between the catalog and the product detail pages.

Models, Collections, and Controllers

Backbone's data layer provides two classes, Model and Collection. To use the Model, you inherit from it, modify the subclasss as needed, and then create new objects from the subclass by constructing the model with a JSON object. You modify the object by calling get() or set() on named attributes, rather than on the Model object directly; this allows Model to notify other interested objects that the object has been changed. And Model comes with fetch() and save() methods that will automatically pull or push a JSON representatino of the model to a server, if the Model has url as one of its attributes.

Collections are just that: lists of objects of a specific model. You extend the Collection class in a child class, and as you do you inform the Collection of what Model it represents, what URL you use to push/pull the full list of objects, and on what field the list should be sorted by default. If you attempt to add a raw JSON object to a collection, it constructs a corresponding Model object out of the JSON and manipulates that.

I will be getting the data from a simplified JSON file that comes in the download; it contains six record albums that the store sells. (Unlike the JSON store, these albums do not exist; the covers were generated during a round of The Album Cover Game, a meme one popular with graphic designers.)

For our purposes, then, we have a Product and a ProductCollection. A popular convention in Backbone is to use concrete names for models, and NameCollection for the collection.

Models are duck-typed by default; they do not care what you put into them. So all I need to say is that a Product is-a Model. The Collection is straightforward as well; I tell it what model it represents, override the initialize() method (which is empty in the Backbone default) to inform this Collection that it has a url, and create the comparator function for default sorting.

Note that Coffeescript uses '@' to represent this, and always returns the last lvalue generated by every function and method. So the last line of initialize below compiles to return this.

<a href="#NWD4SMJMZ-1" name="NW4SMJMZ-46kOnK-1"></a><dfn><product models>=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>)
class Product extends Backbone.Model

class ProductCollection extends Backbone.Collection
    model: Product

    initialize: (models, options) ->
        @url = options.url

    comparator: (item) ->

For the shopping cart, our cart will hold Items, and the cart itself will be an ItemCollection. Shoppings carts are a little odd; the convention is that an Item is not a single instance of a product, but a reference to the products and a quantity.

One thing we will be doing is changing the quantity, so I have provided a convenience function for the Item that allows you to do that. Now, no client classes such as Views need to know how the quantity is updated.

Also, it would be nice to know the total price of the Item.

<a href="#NWD4SMJMZ-2" name="NW4SMJMZ-ixq4z-1"></a><dfn><cart models>=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [D<a href="#NWD4SMJMZ-3">-></a>]
class Item extends Backbone.Model
    update: (amount) ->
        if amount == @get('quantity')
        @set {quantity: amount}, {silent: true}
        @collection.trigger('change', this)

    price: () ->
        @get('product').get('price') * @get('quantity')

The ItemCollection is a little trickier. It is entirely client-side; it has no synchronization with the backend at all. But it does have a model.

The ItemCollection must be able to find an Item in the cart to update when a view needs it. If the Item is not in the Collection, it must create one. The method getOrCreateItemForProduct does this. It uses the detect() method, a method Collection inherits from Backbone's one dependency, Underscore.js; detect() returns the first Item in the ItemCollection for which the function returns true. Also, when I have to create a new Item, I want to add it to the collection, and I pass the parameter silent, which prevents the Collection from notifying event subscribers that the collection has changed. Since this is an Item with zero objects in it, this is not a change to what the collection represents, and I don't want Views to react without having to.

Finally, I add two methods that return the total count of objects in the collection (not Items, but actual Products), and the total cost of those items in the cart. The Underscore method reduce() does this by taking a function for adding progressive items, and a starting value.

<a href="#NWD4SMJMZ-2" name="NW4SMJMZ-ixq4z-2"></a><dfn><cart models>+=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [<a href="#NWD4SMJMZ-2"><-</a>D]
class ItemCollection extends Backbone.Collection
    model: Item

    getOrCreateItemForProduct: (product) ->
        pid = product.get('id')
        i = this.detect (obj) -> (obj.get('product').get('id') == pid)
        if (i)
            return i
        i = new Item
            product: product
            quantity: 0
        @add i, {silent: true}

    getTotalCount: () ->
        addup = (memo, obj) -> obj.get('quantity') + memo
        @reduce addup, 0

    getTotalCost: () ->
        addup = (memo, obj) ->obj.price() + memo
        @reduce(addup, 0);


Backbone Views are simple policy objects. They have a root DOM element, the contents of which they manipulate and to which they listen for events, and a model or collection they represent within that element. Views are not rigid; it's just Javascript and the DOM, and you can hook external events as needed.

More importantly, a View is sensitive to events within its model or collection, and can respond to changes automatically. This way, if you have a rich data ecosystem, when changes to one data item results in a cascade of changes throughout your datasets, the views will receive ``change'' events and can update themselves accordingly.

I will show how this works with the shopping cart widget.

To achieve the fadeIn/fadeOut animations and enforce consistency, I'm going to do some basic object-oriented programming. I'm going to create a base class that contains knowledge about the main area into which all views are rendered, and that manages these transitions.

With this technique, you can do lots of navigation-related tricks: you can highlight where the user is in breadcrumb-style navigation; you can change the class and highlight an entry on a nav bar; you can add and remove tabs from the top of the viewport as needed.

<a href="#NWD4SMJMZ-4" name="NW4SMJMZ-2GA5bM-1"></a><dfn><base view>=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [D<a href="#NWD4SMJMZ-5">-></a>]
class _BaseView extends Backbone.View
    parent: $('#main')
    className: 'viewport'

The above says that I am creating a class called BaseView and defining two fields. The first, 'parent', will be used by all child views to identify into which DOM object the View root element will be rendered. The second defines a common class we will use for the purpose of identifying these views to jQuery. Backbone automatically creates a new DIV object with the class 'viewport' when a view constructor is called. It will be our job to attach that DIV to the DOM. In the HTML, you will see the DIV\#main object where most of the work will be rendered.

<a href="#NWD4SMJMZ-4" name="NW4SMJMZ-2GA5bM-2"></a><dfn><base view>+=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [<a href="#NWD4SMJMZ-4"><-</a>D<a href="#NWD4SMJMZ-6">-></a>]
    initialize: () ->
        @el = $(@el)

The method above ensures that the element is rendered, but not visible, and contained within the DIV\#main. Note also that the element is not a sacrosanct object; the Backbone.View is more a collection of standards than a mechanism of enforcement, and so defining it from a raw DOM object to a jQuery object will not break anything.

Next, we will define the hide and show functions.

Note that in coffeescript, the => operator completely replaces the _.bind() function provided by underscore.

<a href="#NWD4SMJMZ-4" name="NW4SMJMZ-2GA5bM-3"></a><dfn><base view>+=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [<a href="#NWD4SMJMZ-5"><-</a>D]
    hide: () ->
        if not':visible')
            return null
        promise = $.Deferred (dfd) => @el.fadeOut('fast', dfd.resolve)

    show: () ->

        promise = $.Deferred (dfd) => @el.fadeIn('fast', dfd.resolve)

Deferred is a new feature of jQuery. It is a different mechanism for invoking callbacks by attaching attributes and behavior to the callback function. By using this, we can say thing like ``When everything is hidden (when every deferred returned from hide has been resolved), then show the appropriate viewport.'' Deferreds are incredibly powerful, and this is a small taste of what can be done with them.

Before we move on, let's take a look at the HAML we're going to use for our one-page application. The code below compiles beautifully into the same HTML seen in the original Backbone Store.

<a href="#NWD4SMJMZ-7" name="NW4SMJMZ-3cYWdS-1"></a><dfn><index.haml>=</dfn>
!!! 5
%html{:xmlns => ""}
    %title The Backbone Store
    %link{:charset => "utf-8", :href => "jsonstore.css", :rel => "stylesheet", :type => "text/css"}/
    <a href="#NWD4SMJMZ-9" name="NW4SMJMZ-3cYWdS-1-u1"></a><product list template>
    <a href="#NWD4SMJMZ-E" name="NW4SMJMZ-3cYWdS-1-u2"></a><product detail template>
    <a href="#NWD4SMJMZ-H" name="NW4SMJMZ-3cYWdS-1-u3"></a><cart template>
          The Backbone Store
    %script{:src => "jquery-1.6.2.min.js", :type => "text/javascript"}
    %script{:src => "underscore.js", :type => "text/javascript"}
    %script{:src => "backbone.js", :type => "text/javascript"}
    %script{:src => "store.js", :type => "text/javascript"}

It's not much to look at, but already you can see where that DIV\#main goes, as well as where we are putting our templates. The DIV\#main will host a number of viewports, only one of which will be visible at any given time.

Our first view is going to be the product list view, named, well, guess. Or just look down a few lines.

This gives us a chance to discuss one of the big confusions new Backbone users frequently have: What is render() for?. Render is not there to show or hide the view. Render() is there to change the view when the underlying data changes. It renders the data into a view. In our functionality, we use the parent class's show() and hide() methods to actually show the view.

That call to \_super\_ is a Backbone idiom for calling a method on the parent object. It is, as far as anyone knows, the only way to invoke a superclass method if it has been redefined in a subclass. It is rather ugly, but useful.

<a href="#NWD4SMJMZ-8" name="NW4SMJMZ-14ADMh-1"></a><dfn><product list view>=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>)
class ProductListView extends _BaseView
    id: 'productlistview'
    template: $("#store_index_template").html()

    initialize: (options) ->
        @constructor.__super__.initialize.apply @, [options]
        @collection.bind 'reset', _.bind(@render, @)

    render: () ->
        @el.html(_.template(@template, {'products': @collection.toJSON()}))

That _.template() method is provided by undescore.js, and is a full-featured, javascript-based templating method. It's not the fastest or the most feature-complete, but it is more than adequate for our purposes and it means we don't have to import another library. It vaguely resembles ERB from Rails, so if you are familiar with that, you should understand this fairly easily.

And here is the HAML:

<a href="#NWD4SMJMZ-9" name="NW4SMJMZ-1uC8r-1"></a><dfn><product list template>=</dfn> (<a href="#NWD4SMJMZ-7"><-U</a>)
  %h1 Product Catalog
    <% for(i=0,l=products.length;i<l;++i) { p = products[i]; %>
        %a{:href => "#item/<%= %>"}
          %img{:src => "<%= p.image %>", :alt => "<%= p.title %>"}/
      .item-artist <%= p.artist %>
      .item-title <%= p.title %>
      .item-price $<%= p.price %>
    <% } %>

One of the most complicated objects in our ecosystem is the product view. It actually does something! The prefix ought to be familiar, but note that we are again using \#main as our target; we will be showing and hiding the various DIV objects in \#main again and again.

The only trickiness here is twofold: the (rather hideous) means by which one calls the method of a parnt class from a child class via Backbone's class heirarchy (this is most definitely not Javascript standard), and keeping track of the itemcollection object, so we can add and change items as needed.

<a href="#NWD4SMJMZ-A" name="NW4SMJMZ-1JDx2-1"></a><dfn><product detail view>=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [D<a href="#NWD4SMJMZ-B">-></a>]
class ProductView extends _BaseView
    id: 'productitemview'
    template: $("#store_item_template").html()
    initialize: (options) ->
            @constructor.__super__.initialize.apply @, [options]
            @itemcollection = options.itemcollection
            @item = @itemcollection.getOrCreateItemForProduct @model

There are certain events in which we're interested: keypresses and clicks on the update button and the quantity form. (Okay, UQ'' isn't the best for update quantity''. I admit that.) Note the peculiar syntax of EVENT SELECTOR'': methodByName'' for each event.

Backbone tells us that the only events it can track by itself are those that jQuery's ``delegate'' understands. As of 1.5, that seems to be just about all of them.

<a href="#NWD4SMJMZ-A" name="NW4SMJMZ-1JDx2-2"></a><dfn><product detail view>+=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [<a href="#NWD4SMJMZ-A"><-</a>D<a href="#NWD4SMJMZ-C">-></a>]
        "keypress .uqf" : "updateOnEnter"
        "click .uq"     : "update"

And now we will deal with the update. This code ought to be fairly readable: the only specialness is that it's receiving an event, and we're ``silencing'' the call to cart.add(), which means that the cart collection will not publish any events. There are only events when the item has more than zero, and that gets called on cart_item.update().

In the original tutorial, this code had a lot of responsibility for managing the shopping cart, looking into it and seeing if it had an item for this product, and there was lots of accessing the model to get its id and so forth. All of that has been put into the shopping cart model, which is where it belongs: knowledge about items and each item's relationship to its collection belongs in the collection.

Look closely at the update() method. The reference @\$ is a special Backbone object that limits selectors to objects inside the element of the view. Without it, jQuery would have found the first input field of class 'uqf' in the DOM, not the one for this specific view. @\$('.uqf') is shorthand for $('uqf', @el), and helps clarify what it is you're looking for.

<a href="#NWD4SMJMZ-A" name="NW4SMJMZ-1JDx2-3"></a><dfn><product detail view>+=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [<a href="#NWD4SMJMZ-B"><-</a>D<a href="#NWD4SMJMZ-D">-></a>]
    update: (e) ->
        @item.update parseInt(@$('.uqf').val())

    updateOnEnter: (e) ->
        if (e.keyCode == 13)
            @update e

The render is straightforward:

<a href="#NWD4SMJMZ-A" name="NW4SMJMZ-1JDx2-4"></a><dfn><product detail view>+=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [<a href="#NWD4SMJMZ-C"><-</a>D]
    render: () ->
        @el.html(_.template(@template, @model.toJSON()))

The product detail template is fairly straightforward. There is no underscore magic because there are no loops.

<a href="#NWD4SMJMZ-E" name="NW4SMJMZ-3QlVWl-1"></a><dfn><product detail template>=</dfn> (<a href="#NWD4SMJMZ-7"><-U</a>)
%script#store_item_template(type= "text/x-underscore-template")
      %img(src="<%= large_image %>" alt="<%= title %>")/
      .item-artist <%= artist %>
      .item-title <%= title %>
      .item-price $<%= price %>
      %form(action="#/cart" method="post")
          %label Quantity:
          %input(type="text" size="2" name="quantity" value="1" class="uqf")/
          %input(type="submit" value="Add to Cart" class="uq")/

        %a(href="<%= url %>") Buy this item on Amazon
        %a(href="#") &laquo; Back to Items

So, let's talk about that shopping cart thing. We've been making the point that when it changes, when you call item.update within the product detail view, any corresponding subscribing views sholud automatically update.

<a href="#NWD4SMJMZ-F" name="NW4SMJMZ-f68W1-1"></a><dfn><cart widget>=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [D<a href="#NWD4SMJMZ-G">-></a>]
class CartWidget extends Backbone.View
    el: $('.cart-info')
    template: $('#store_cart_template').html()

    initialize: () ->
        @collection.bind('change', _.bind(@render, @));

And there is the major magic. CartWidget will be initialized with the ItemCollection; when there is any change in the collection, the widget will receive the 'change' event, which will automatically trigger the call to the widget's render() method.

The render method will refill that widget's HTML with a re-rendered template with the new count and cost, and then wiggle it a little to show that it did changed:

<a href="#NWD4SMJMZ-F" name="NW4SMJMZ-f68W1-2"></a><dfn><cart widget>+=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [<a href="#NWD4SMJMZ-F"><-</a>D]
    render: () ->
        tel = @el.html _.template @template,
            'count': @collection.getTotalCount()
            'cost': @collection.getTotalCost()
        tel.animate({paddingTop: '30px'}).animate({paddingTop: '10px'})

And the HTML for the template is dead simple:

<a href="#NWD4SMJMZ-H" name="NW4SMJMZ-4MHorL-1"></a><dfn><cart template>=</dfn> (<a href="#NWD4SMJMZ-7"><-U</a>)
  %p Items: <%= count %> ($<%= cost %>)

Lastly, there is the Router. In Backbone, the Router is a specialized View for invoking other views. It listens for one specific event: when the window.location.hash object, the part of the URL after the hash symbol, changes. When the hash changes, the Router invokes an event handler. The Router, since its purpose is to control the major components of the one-page display, is also a good place to keep all the major components of the sytem. We'll keep track of the Views, the ProductCollection, and the ItemCollection.

<a href="#NWD4SMJMZ-I" name="NW4SMJMZ-1RT8U1-1"></a><dfn><router>=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [D<a href="#NWD4SMJMZ-J">-></a>]
class BackboneStore extends Backbone.Router
    views: {}
    products: null
    cart: null

There are two events we care about: view the list, and view a detail. They are routed like this:

<a href="#NWD4SMJMZ-I" name="NW4SMJMZ-1RT8U1-2"></a><dfn><router>+=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [<a href="#NWD4SMJMZ-I"><-</a>D<a href="#NWD4SMJMZ-K">-></a>]
        "": "index"
        "item/:id": "product"

Like most Backbone objects, the Router has an initialization feature. I create a new, empty shopping cart and corresponding cart widget, which doesn't render because it's empty. I then create a new ProductCollection and and corresponding ProductListView. These are all processes that happen immediately.

What does not happen immediately is the fetch() of data from the back-end server. For that, I use the jQuery deferred again, because fetch() ultimately returns the results of sync(), which returns the result of an ajax() call, which is a deferred.

<a href="#NWD4SMJMZ-I" name="NW4SMJMZ-1RT8U1-3"></a><dfn><router>+=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [<a href="#NWD4SMJMZ-J"><-</a>D<a href="#NWD4SMJMZ-L">-></a>]
    initialize: (data) ->
        @cart = new ItemCollection()
        new CartWidget
            collection: @cart

        @products = new ProductCollection [],
            url: 'data/items.json'
        @views =
            '_index': new ProductListView
                collection: @products
        $.when(@products.fetch({reset: true}))
            .then(() -> window.location.hash = '')

There are two things to route to, but we must also route from. Remember that our two major views, the product list and the product detail, inherited from \_BaseView, which has the hide() and show() methods. We want to hide all the views, then show the one invoked. First, let's hide every view we know about. hide() returns either a deferred (if the object is being hidden) or null. The call at the end means that this method returns only an array of deferreds.

<a href="#NWD4SMJMZ-I" name="NW4SMJMZ-1RT8U1-4"></a><dfn><router>+=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [<a href="#NWD4SMJMZ-K"><-</a>D<a href="#NWD4SMJMZ-M">-></a>]
    hideAllViews: () ->, (v) -> return v.hide()),
            (t) -> t != null)

Showing the product list view is basically hiding everything, then showing the index:

<a href="#NWD4SMJMZ-I" name="NW4SMJMZ-1RT8U1-5"></a><dfn><router>+=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [<a href="#NWD4SMJMZ-L"><-</a>D<a href="#NWD4SMJMZ-N">-></a>]
    index: () ->
        view = @views['_index']
        $.when(@hideAllViews()).then(() ->

On the other hand, showing the product detail page is a bit trickier. In order to avoid re-rendering all the time, I am going to create a view for every product in which the user shows interest, and keep it around, showing it a second time if the user wants to see it a second time.

Not that we pass it the ItemCollection instance. It uses this to create a new item, which (if you recall from our discussion of getOrCreateItemForProduct()) is automagically put into the collection as needed. Which means all we need to do is update this item and the item collection changes, which in turn causes the CartWidget to update automagically as well.

<a href="#NWD4SMJMZ-I" name="NW4SMJMZ-1RT8U1-6"></a><dfn><router>+=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>) [<a href="#NWD4SMJMZ-M"><-</a>D]
    product: (id) ->
        product = @products.detect (p) -> p.get('id') == (id)
        view = (@views['item.' + id] ||= new ProductView(
            model: product,
            itemcollection: @cart
            () ->

Finally, we need to start the program

<a href="#NWD4SMJMZ-O" name="NW4SMJMZ-3GGy0P-1"></a><dfn><initialization>=</dfn> (<a href="#NWD4SMJMZ-P">U-></a>)
$ ->
    new BackboneStore()

The Program

Here's the entirety of the program. Coffeescript provides its own namespace wrapper:

<a href="#NWD4SMJMZ-P" name="NW4SMJMZ-1YuVt9-1"></a><dfn><>=</dfn>
<a href="#NWD4SMJMZ-1" name="NW4SMJMZ-1YuVt9-1-u1"></a><product models>

<a href="#NWD4SMJMZ-2" name="NW4SMJMZ-1YuVt9-1-u2"></a><cart models>

<a href="#NWD4SMJMZ-4" name="NW4SMJMZ-1YuVt9-1-u3"></a><base view>

<a href="#NWD4SMJMZ-8" name="NW4SMJMZ-1YuVt9-1-u4"></a><product list view>

<a href="#NWD4SMJMZ-A" name="NW4SMJMZ-1YuVt9-1-u5"></a><product detail view>

<a href="#NWD4SMJMZ-F" name="NW4SMJMZ-1YuVt9-1-u6"></a><cart widget>

<a href="#NWD4SMJMZ-I" name="NW4SMJMZ-1YuVt9-1-u7"></a><router>

<a href="#NWD4SMJMZ-O" name="NW4SMJMZ-1YuVt9-1-u8"></a><initialization>


None of these formats are native to the browser, so getting them into the browser requires a compilation step. Here are the basic compilation steps for these three pieces of code:

haml --unix-newlines --no-escape-attrs --double-quote-attribute index.haml > index.html
coffee -compile
stylus jsonstore.styl

I hope in the future to provide a Cakefile (a makefile alternative written in Cake) for your amusement.

A Little Stylus

Stylus is a beautiful little language that compiles down to CSS. The original version of The Backbone Store used the same CSS provided from the original Sammy tutorial, but I wanted to show you this one extra tool because it's an essential part of my kit.

If you want rounded borders, you know that writing all that code, for older browsers as well as modern ones, and providing it to all the different objects you want styled that way, can be time consuming. Stylus allows you to define a function that can be called from within any style, thus allowing you to define the style here, and attach a set style to a semantic value in your HTML:

<a href="#NWD4SMJMZ-Q" name="NW4SMJMZ-3AObZp-1"></a><dfn><jsonstore.styl>=</dfn> [D<a href="#NWD4SMJMZ-R">-></a>]
  -moz-border-radius-topleft: radius
  -moz-border-radius-topright: radius
  -moz-border-radius-bottomleft: radius
  -moz-border-radius-bottomright: radius
  -webkit-border-bottom-right-radius: radius
  -webkit-border-top-left-radius: radius
  -webkit-border-top-right-radius: radius
  -webkit-border-bottom-left-radius: radius
  border-bottom-right-radius: radius
  border-top-left-radius: radius
  border-top-right-radius: radius
  border-bottom-left-radius: radius

  background: base
  background: -webkit-gradient(linear, left top, left bottom, from(lighten(base, 20%)), to(darken(base, 20%)))
  background: -moz-linear-gradient(top,  lighten(base, 20%), darken(base, 20%))

And if you look down below you'll see the rounded() function called for the list items, which have borders.

One of the real beauties of Stylus is that you can contains some style definitions within others. You can see below that the header contains an H1, and the H1 definitions will be compiled to only apply within the context of the header. Stylus allows you to write CSS the way you write HTML!

<a href="#NWD4SMJMZ-Q" name="NW4SMJMZ-3AObZp-2"></a><dfn><jsonstore.styl>+=</dfn> [<a href="#NWD4SMJMZ-Q"><-</a>D]
  font-family: "Lucida Grande", Lucida, Helvetica, Arial, sans-serif
  background: #FFF
  color: #333
  margin: 0px
  padding: 0px

  margin: 0px
  padding: 20px
  border-bottom: 1px solid #ccc

    font-family: Inconsolata, Monaco, Courier, mono
    color: #FFF
    margin: 0px

    position: absolute
    top: 0px
    right: 0px
    text-align: right
    padding: 10px
    color: #FFF
    font-size: 12px
    font-weight: bold

  border: 0

    list-style: none

  width: 250px
  margin-right: 10px
  margin-bottom: 10px
  padding: 5px
  border: 1px solid #ccc
  font-size: 12px

  font-weight: bold

  font-weight: bold
  font-size: 14px

  margin: 10px 0 0 10px

    margin-right: 10px

    padding: 100px 10px 0px 10px

  * _<base view>_: D1, D2, D3, U4
  * _<cart models>_: D1, D2, U3
  * _<cart template>_: U1, D2
  * _<cart widget>_: D1, D2, U3
  * _<index.haml>_: D1
  * _<initialization>_: D1, U2
  * _<jsonstore.styl>_: D1, D2
  * _<product detail template>_: U1, D2
  * _<product detail view>_: D1, D2, D3, D4, U5
  * _<product list template>_: U1, D2
  * _<product list view>_: D1, U2
  * _<product models>_: D1, U2
  * _<router>_: D1, D2, D3, D4, D5, D6, U7
  * _<>_: D1

And that's it. Put it all together, and you've got yourself a working Backbone Store.

This code is available at my github at The Backbone Store, modern branch.  This branch includes the current Makefile, as well as the native noweb document.