Mutating ``exports`` in a function call is not something that you normally see in a node-style module. It works out given our pattern of modules as singleton controllers that must be "booted up" via an ``init`` method, but it will break down if we ever need 2 inline edit forms on the same page.

I'm on board with merging this working version, but I'd like to look into a broader refactoring of our singleton modules so they return Django-style constructors that close over their options.

```javascript
exports = function(options) {
   ... internal setup ...
    return {
      isEditModePropery: ...
   }
}

... at the top of a page controller  ...
var InlineEditForm = require('./inlineEditForm')
... later...
plotEditForm = InlineEditForm(options)
plotEditForm.inEditModeProperty.assign(...)