Comments on: Backbone.js: Getting The Model For A Clicked Element

By: Alex Pavlov

Alex Pavlov — Sun, 05 May 2013 13:24:00 +0000

Is it possible to link (with “a href=’someView/{{id}}’” which is defined on Router) each list item to view?

By: Jed

Jed — Sun, 20 Jan 2013 23:13:00 +0000

Also, it makes debugging a bit more difficult. It’s nice to be able to see the model id that the DOM element is associated with, without having to compare attributes or pause a click event.

By: Jed

Jed — Thu, 17 Jan 2013 20:23:00 +0000

This is a great demo of two approaches. Two things that are important to mention about the second approach, however, are: 1) It requires rendering in a loop, which is bad, especially with larger lists. It should be a major priority to minimize writes to the DOM; 2) It binds events to every rendered dom element in a collection, rather than binding once to the closest common ancestor and delegating from there. With a large list, this is a ton of extra noise and management. If you want to unbind the click temporarily, for example, you have to unbind many elements instead of one. The tagName thing is also a little suspect in an otherwise template-based system.

By: Rob Nugen

Rob Nugen — Wed, 14 Nov 2012 01:20:00 +0000

Your articles are really helpful, and they could be even better if “its” was used at it’s intended. http://how-to-spell-its.com/ for reference.

By: LazyBucks.net

LazyBucks.net — Wed, 05 Sep 2012 20:27:00 +0000

And pretty much every instance of “it’s” should be “its.” “It’s” = “it is.”

I guess that can be considered nit-picky but it’s really distracting.

By: Derick Bailey

Derick Bailey — Fri, 03 Aug 2012 01:06:00 +0000

the call to “this.collection.each” takes in a function as a callback to process each of the items: this.collection.each(function(item){ … }); instead of providing an inline function directly, though, I’m using “this.renderItem” as a callback function – basically, a method pointer. So, when the “collection.each” iterates over each function, it calls the “renderItem” function, passing the “item” argument along to it.

Pardon the self-promotion for a moment: if you’re interested in seeing more about how this works, and all the surrounding, I have a (paid) screencast that discusses callback functions and many other ways to execute a function, here: http://www.watchmecode.net/javascript-context There are, of course, a thousand other resources for learning more about this, online :)

By: Ryan Craftman

Ryan Craftman — Thu, 02 Aug 2012 22:40:00 +0000

Great article – thanks. I am a complete newbie when it comes to Backbone.js. MVC and all of that is fine and we understand it, but to wrap how Backbone works in that world is taking some getting used to and I can say its definitely not easy even for someone experienced and knows everything about MVC.

Quick question because I think am a little lost.

renderItem: function(model) takes model parameter when called.

But it is invoked like so: this.collection.each(this.renderItem);

No model object was passed into renderItem. What am I missing?

Thanks for the great article again.

By: Andreas

Andreas — Thu, 12 Apr 2012 12:48:00 +0000

Thanks.

I’ve seen and read about your marionette project before but right now I think I need to get a better understanding of backbone it self, having to taste the boilerplate stuff you have gone through that led you to building marionette, before I could take advantage of it.

By: Derick Bailey

Derick Bailey — Thu, 12 Apr 2012 12:44:00 +0000

yes. passing the raw model to a template is just going to make things difficult. you’ll end up writing a lot of “get(‘whatever’)” code in your templates, which will get old and frustrating fast.

fwiw, i’ve wrapped up template rendering in my Backbone.Marionette framework so that I never have to think about this anymore: https://github.com/derickbailey/backbone.marionette

By: Andreas

Andreas — Thu, 12 Apr 2012 12:42:00 +0000

so you always pass your models and collections as json to your templates?