Question

I’m trying to wrap my head around backbone.js but I’m finding it hard due to the lack of (IMO) good examples.

First of all, what is the best way of getting a link to an object.
If I want to get the edit url of an Album model I could do album.url() + '/edit', is this really the best way?

Also, I’m trying to make my application work 100% without javascript so I don’t want my URLs/links to say /albums/#1/edit, I want it to be /albums/1/edit and override this in JS.

I’m thinking I create normal URLs and use jQuery.live to call router.navigate in backbone.js
I never got this to work however, when I call router.navigate('/albums/2', true) the URL changes but my show action is never called. If I refresh it’s called so the route is matched.

What am I missing?

Answer 1

The basic answer, which is kind of frustrating, is “there is no preferred way!”. Backbone.js doesn’t tell you how to set up links, you can do it any way you like. I found this flexibility just as annoying as you do, at least at first.

So here’s the way I’m approaching this on my current project, with the (big) caveat that this is just one of many ways to do things in Backbone:

• For the most part, I don’t use actual links. There’s no explicit reason not to, but it means you have to keep track of a bunch of URL strings that have to be consistent. I would rather stick all the URL formatting in my routers and not deal with it elsewhere.

• To open a new “top-level” view, like an editing screen, I set something that fires an event. In the application I’m currently working on, I have a global State model, and to open a new view I call state.set({ topview: MyTopView }). This causes the state object to trigger change:topview.

• Any piece of the UI that needs to change when the top-level view changes has an update method bound to change:topview. When the event fires, they look at state.get('topview') and update as necessary.

• I treat my routers as only marginally specialized parts of the UI – they’re essentially views that render in the browser address bar, rather than the window. Like other views, they update the state object on UI events (i.e. a new URL), and like other views, they listen to the state object for changes that cause them to update. The logic that the editing screen has the URL albums/<albumid>/edit is fully encapsulated in the router, and I don’t refer to it anywhere else.

This works well for me, but it adds an entirely new pattern, the global State object, to the Backbone structure, so I can hardly call this the “preferred” approach.

Update: Also note that .url(), in the Backbone idiom, refers to the model’s URL in the back-end API, not the front-end URL (it’s not like Django’s get_absolute_url). There is no method in the default Backbone setup that gives you a user-facing URL for your model – you’d have to write this yourself.