Comments on: Stop Using Backbone As If It Were A Stateless Web Server

By: Christian Mauceri

Christian Mauceri — Tue, 26 Mar 2013 22:29:00 +0000

Really great article, I agree with Gert Delete me makes more sense to avoid to get back to the root in a modal view for instance. Anyway thanks a lot !

By: Jeremy Schwartz

Jeremy Schwartz — Fri, 01 Feb 2013 13:44:00 +0000

Devil’s advocate – class makes more sense:
1) I’m assuming class selectors are more efficient than data-attribute selectors, as some browsers have the native `getElementsByClassName`
2) using class can double-duty with visual cues — not only do you target it for behavior, but you can use the same CSS to (as you say, more appropriately) style it with a delete icon, etc.
3) fits with the OOCSS (object-oriented css) pattern

I usually prefer something more indicative of the fact that it is a delete action — `btn-delete` or `actn-delete` rather than just `delete`, so you can take advantage of OOCSS like:

{a href=”btn btn-delete”}Delete{/a}

then CSS
.btn { width: 16px; height: 16px; text-indent:… }
.btn-delete { background-image:url(delete-icon.png); }

then JS
$(‘.btn-delete’).click…

or even
$(‘.btn’).click( // all buttons fire, then you can check for extended class to determine what happens specifically

By: Rocket

Rocket — Fri, 14 Sep 2012 16:50:00 +0000

I’ve seen another approach where the views for models are being stored in a cache. To remove a view you just look it up in the list and call .remove().This way we have symmetry – both adding and removing of views is done on the same level, in collection view. As opposed to adding views in collection view, and removing in model view (as you described). Which way do you think is better?

By: bob

bob — Tue, 04 Sep 2012 18:49:00 +0000

i finally read your post. I was wondering if it creates a larger memory footprint to bind each individual event on a view. Ie.You have a list of elements. Each element has a delete button. You can bind the delete event to each element vs binding the delete event to the list and have event propagation handle each elements delete.

By: Gert

Gert — Sun, 27 May 2012 14:38:00 +0000

Great article, I completely agree with you. I wouldn’t use the class attribute to bind the actions though, it should be for CSS only imho. What I do is:

Delete me

and

events: { ”click a[data-action=delete]“: “delete” }

This just makes more sense to me personally.

By: Libor Nenadál

Libor Nenadál — Tue, 08 May 2012 15:35:00 +0000

Well quite a lot of words for one simple thing – use route for routing to items (views), not for actions. ;-)

By: Dude

Dude — Fri, 30 Mar 2012 18:53:00 +0000

isn’t this stuff obvious? i’m shocked, honestly

By: A'braham Barakhyahu

A'braham Barakhyahu — Wed, 24 Aug 2011 16:03:00 +0000

Others have echoed my sentiments. Web devs that have been so used to stateless nature of the web do need to look at clientside-apps like desktop applications. Good post.

By: Anonymous

Anonymous — Sat, 13 Aug 2011 17:53:00 +0000

I’ve not had any problems using it. Really it’s just a shortened version of

By: Derick Bailey

Derick Bailey — Sat, 13 Aug 2011 15:49:00 +0000

that’s interesting… i don’t think i’ve seen that one before. is that supported by all the major browsers?