Question

I’m building my first Backbone.js app and I’m confused about how much responsibility I’m supposed to give to or hide from my Views.

In my example, I’m building a Rich UI Table (similar to YUI’s datagrid) that’s dynamically generated from a Collection. In my app I call this an “AppTable”. In my understanding of MVC, I would imagine that there’d be some kind of AppTable controller which finds the correct Collection, grabs a “dumb” View and passes to the View whatever information from the Collection it needs to render. In this senario, the View would do little more than take the data provided to it and modify the DOM accordingly, maybe even populating a template or attaching event listeners.

Backbone seems to do away with the idea of having a controller mediate between the View and Collection. Instead a View gets initialized with a reference to a Collection and it is View’s responsibility to update itself.

Am I understanding this architecture correctly?

Assuming I do, my question then becomes, what happens when my View needs to do more and more? For example, I want column sorting, drag-and-drop for rows, pagination, searching, table control links (like new, copy, delete row… etc), and more. If we stick with a “smart” View paradigm where the View is connected directly to a Collection, do the above functions become attached to View object?

Thinking through this, I could see the View growing from a simple table wrapper to pretty messy beast with lot of functionality attached to it. So, is the View really a controller in this case?

Answer 1

Your understanding of the architecture is correct. Backbone does not recognize the concept of a “controller” in the traditional MVC sense. (In fact, Backbone used to actually have an object called a Controller, but it has been renamed Router to more accurately describe what it does.)

The functions you list (drag-drop, delete rows, sorting, etc.) would all belong in a View. A view describes what you see and responds to user input. Anything involving an event (a click, a keypress, a submit, etc.) all go inside of a view. But your view should never actually manipulate the data; that should be done by its model. You are correct in thinking that a view acts like a controller, because it packages data and sends it to the model, which will then validate/set/save appropriately. Once those actions have occurred, the view re-renders itself to represent the new version of the data inside the model.

One note of caution: your view should not be too strenuously tied to the DOM. It is Backbone convention to have a top-level DOM element that your view is tied to (e.g., a form or a div) and then deal only with its sub-elements. That is appropriate; in general, things like “remove this link from this div” inside your view are not. If you find your view growing unwieldy, you most likely need to break it into subviews, each with their respective behaviors as components of their whole.