Aha!  Now I get it.  But would this only work for the "root" view that is bound to the context?  What about sub-views that are assigned later?  Usually for sub-views, I do this wiring manually, like:

```js
//root-view.js
render: function() {
  var childView = new ChildView({ context: this.context });
  childView.render();
}

//child-view.js
initialize: function() {
  this.context = this.options.context;
  this.context.listen(this, "foo", handleFoo);
  this.context.listen(this, "bar", handleBar);
}
```

This logic (assigning a sub-view to a context, and registering context listeners on that sub-view) looks like it could be a good candidate for refactoring according to your pattern.  Maybe something like:

```js
//child-view.js
contextEvents: {
  "foo": "handleFoo",
  "bar": "handleBar"
}
initialize: function() {
  Geppetto.bindContext({
    context: this.options.context
  });
}
```

What do you think about that?  

Of course, the next question is, should we overload the existing `bindContext` method for attaching sub-views, as well as parent views, or create a new explicit method for this?

If we use the existing method, it would be harder to communicate our intention and might be confusing.

Perhaps we should create another method, like `setContext` which would do everything that `bindContext` does except that it would not:
1. Set a view property on the context
2. Attach an onClose handler to the view
3. Try to instantiate a new context object