Break out your shared Backbone.js model/collection/view behaviors into separate modules and mix them into your classes with Cocktail - an implementation of Backbone mixins.
Mixins are simply bare-bones JavaScript objects that provide additional functionality to your Backbone objects. Think of them as bags of methods that will get added to all instances of your objects.
Here's an example mixin that implements selectability on a view based on a model's selection state:
window.MyMixins = {};
MyMixins.SelectMixin = {
initialize: function() {
this.model.on('change:selected', this.refreshSelect, this);
},
events: {
click: 'toggleSelect'
},
render: function() {
this.refreshSelect();
},
refreshSelect: function() {
this.$el.toggleClass('selected', this.model.get('selected'));
},
toggleSelect: function() {
this.model.set('selected', !this.model.get('selected'));
}
}
As you can see: nothing special, just a bag of functions.
Obviously, the bit about
window.MyMixinsis just a suggested pattern for organizing your mixins!
And, yes, having models know about view state like selection is often an anti-pattern... but it makes for a simple intelligible example!
Once you have your mixins defin;;ed including them in your Backbone object definitions is a one-liner:
var MyView = Backbone.View.extend({
mixins: [MyMixins.SelectMixin, MyMixins.SomeOtherMixin],
events: {
'click .myChild': 'myCustomHandler'
}
initialize: function() {
...
},
render: function() {
...
},
etc...
});
Now all instances of MyView will have the selection behavior defined in the SelectMixin:
var view = new MyView(...);
view.toggleSelect(); //works!
In the example above, both MyView and SelectMixin both defined initialize, and render. What happens with these colliding methods?
Cocktail automatically ensures that methods defined in your mixins do not obliterate the corresponding methods in your classes. This is accomplished by wrapping all colliding methods into a new method that is then assigned to the final composite object.
Let's take a concrete example. Class X implements render and mixes in mixins A, B, and C (in that order). Of these only A and C implement render.
When render is called on instances of X the implementation of render in X is called first, followed by the implementation in A and then C. In this way the original implementation is always called first, followed by the mixins.
The return value of the composite function is the last non-undefined return value from the chain of colliding functions.
To be clear: let's say X mixes in A and B. Say X implements a method foo that returns bar, A implements foo but returns nothing (i.e. undefined is implicitly returned) and B implements baz. Then instances of X will return baz -- the last non-undefined return value from foo's X → A → B collision chain.
The events hash is special-cased by Cocktail. Mixins can define new events hashes. The set of event hashes (original implementation + each mixin) are merged together.
Note that key-collisions are still possible. If two mixins add a click handler to the events hash ({'click': ... }) then the last mixin in the mixins list's event handler will win.
Subclass hierarchies with mixins should work just fine. If a super class mixes in a mixin, then all subclasses will inherit that mixin. If those subclasses mixin additional mixins, those mixins will be folded in to the subclasses and collisions will be handled correctly, even collisions with methods further up the class hierarchy.
However, if a subclass redefines a method that is provided by a mixin of the super class, the mixin's implementation will not be called. This shouldn't be surprising: the subclass's method is further up in the prototype chain and is the method that gets evaluated. In these circumstance you must remember to call SubClass.__super__.theMethod.apply(this) to ensure that the mixin's method gets called.
The example directory includes an example mixin and its usage, and the accompanying Jasmine test. It also includes a readme that walks through the testing pattern employed for testing mixins with Jasmine.
Cocktail requires:
- Backbone (duh) (tested with 0.9.2)
- Underscore (tested with 1.3.3)
To use Cocktail you must include Cocktail.js it after including Underscore and Backbone. Cocktail monkey-patches backbone's extend!
Future changes to backbone could break Cocktail or obviate its need. If the latter happens - great! If the former: let me know and I'll try to ensure compatibility going forward.
...check out Coccyx. Coccyx helps you plug up backbone leaks with two things: named constructors and tear-downable view hierarchies.