We've done a lot of new and interesting things in this chapter. The most difficult part was getting the hover effect. It required us to find all the views that represented a single model instance. Most of the time, in a Backbone application, you'll have a single view representing a model instance at a time. However, as you've seen here, while this is the norm, it certainly isn't the only way possible.

The other neat use of Backbone was the Month class that we created. We're really just using it as a handy wrapper; there's no reason we couldn't have written a simple function that returned an object literal. However, the way we've done it shows off the flexibility of Backbone.

The last, but arguably most important, idea from this chapter is the idea of moving appropriate logic into the model class, instead of putting it in the view class. Good examples of this are the App.Models.Calendar class's onDate method or the App.Models.Event class's hours method. This is one of the big ideas...