Methods .fetch(), .save() and .destroy() on Backbone.Model are checking if the model has .sync() defined and if yes it will get called otherwise Backbone.sync() will get called (see the last lines of the linked source code). So one of the solutions is to implement .sync() method. Example: var User = Backbone.Model.extend({ // … methodToURL: { … Read more
Options passed into the constructor are automatically stored as this.options var myView = Backbone.View.extend({ myVar : ‘Hello from inside’, initialize: function() { alert(this.options.myVar); } )}; new myView({myVar: ‘Hello from outside’});
Partial rendering of views In order to minimize the full rendering of your DOM hierarchy, you can set up special nodes in your DOM that will reflect updates on a given property. Let’s use this simple Underscore template, a list of names: <ul> <% _(children).each(function(model) { %> <li> <span class=”model-<%= model.cid %>-name”><%= model.name %></span> : … Read more
There seems to be some confusion about what Router#navigate does exactly, I think. Without any options set it will update the URL to the fragment provided. E.g. router.navigate(‘todo/4/edit’) will update the URL to #todo/4 AND will create a browser history entry for that URL. No route handlers are run. However, setting trigger:true will update the … Read more
Usually REST backends handle single instance creation/update. You would need to change that to accept an array of objects. That said, on the client side, you would need to go directly to the Backbone.sync function Backbone.sync = function(method, model, options) In this case your model should be an array of model. The method should be … Read more
My shop uses .handlebars, along with Require.js and Alex Sexton’s require-handlebars plug-in, and it all works without issue. The far more common suffix however, and the default one in that plug-in I just mentioned, is .hbs (presumably because .hbs is a 3-character extension not already taken by another file type). You can for example use … Read more
There is the “route” event on the Router: http://backbonejs.org/#Events-catalog “route” (router, route, params) — Fired by history (or router) when any route has been matched. This allows you to bind to specific routes. If you want to fire a handler after any route, bind to “route”, and the route will be the first argument: myRouter.on(“route”, … Read more
To clear things a little bit here. A Router is not a Controller, It’s a way to define a client-side route map (similar to Rails’s routes.rb). This helps routing client-side pages to certain actions/handlers. And that’s different from a controller’s job which is to provide a bit of orchestration between Models and Views. And there … Read more
It might not be obvious, but event property in backbone.js views is used only for DOM events. Custom events should be bound as James Brown mentioned above.
Backbone from NPM via JSPM