Comments on: Zombies! RUN! (Managing Page Transitions In Backbone Apps)

By: Vikram Pawar

Vikram Pawar — Sun, 12 May 2013 18:12:00 +0000

Thanks dude. You’re a life saver!

By: Sam

Sam — Thu, 09 May 2013 16:21:00 +0000

Please use new Backbone.Events.listenTo instead of Backbone.Events.on

By: Vignesh Nandha Kumar

Vignesh Nandha Kumar — Thu, 02 May 2013 07:08:00 +0000

Hi, isn’t the problem we are trying to solve by adding the `onClose` callback already solved by `stopListening`, which is called automatically by Backbone during `view.remove`?

By: Joel Kemp

Joel Kemp — Fri, 01 Mar 2013 23:06:00 +0000

Bless your soul.

By: m4cm3nz

m4cm3nz — Fri, 01 Mar 2013 17:45:00 +0000

Great!! I really don’t like the blog’s logo and layout, but the content is awesome

By: Neil Young

Neil Young — Fri, 01 Mar 2013 11:59:00 +0000

Thanks for the great code although I am finding using this kills the events in my views when using your app view as the events are setup on the element in the object and then added to the #mainContent div ?

By: jami

jami — Mon, 25 Feb 2013 20:39:00 +0000

Thanks for such a comprehensive post.

I had what I thought were zombies, but no, it was just that I was instantiating a view twice with the same event, and I only wanted it to fire for one of the instances. I solved it by taking the events out on instantiation and using Backbone’s delegateEvents() function when I needed the event to be bound.

By: Thalis Kalfigkopoulos

Thalis Kalfigkopoulos — Mon, 18 Feb 2013 15:40:00 +0000

I may be mistaken, but shouldn’t line 3 of the Appview definition be:

this.showView = function(view) {…}

Instead of the shown:

this.showView(view) {…}

By: Michael Mitchell

Michael Mitchell — Sun, 10 Feb 2013 21:05:00 +0000

You are awesome. Thank you for this.

By: Derick Bailey

Derick Bailey — Wed, 06 Feb 2013 15:17:00 +0000

yes it does. i said that wrong in the article