view.stopListening

[scottastrophic]

The key difference between view.remove() in backbone proper and view.tearDown() in coccyx is the presence in the former of view.stopListening. Is this something that should be added to that method? In our project we've been relying on tearDown instead of remove (as per the coccyx docs) and traced a nasty bug back to a listenTo that was still bound to a view we had torn down.

[onsi]

The short answer is that, yes, a call to view.stopListening should be added to tearDown. I've been meaning to get around to this but haven't had much time to devote to Coccyx (I've been writing more Objective C than JS lately!)

The long answer, however, is that between listenTo, stopListening, and remove Backbone 1.0 now goes a long way towards solving the central problem that coccyx was built to solve: tearing down event bindings to avoid memory leaks. The one thing that coccyx provides that the backbone does not is a means to track view hierarchies -- but this is a relatively simple part of the problem.

So... I'll try to find some time to add stopListening to tearDown soon. But I'll be updating the Readme to encourage people to start using Backbone's emerging patterns for removing views and to start moving away from coccyx (hooray!).