I suspect there will probably be problems using the MutationObserver that was setup for contenteditable with aloha.

There's 2 places where the aloha code would need to go: 1) `when 'aloha' then console.log 'FIX: enable aloha'` under `_makeEditable()` to enable aloha for the given element(s) as defined by the `$editable` variable, and under `_makeUneditable()` to disable aloha (dummy code is already in place for each).  `_makeUneditable()` is just the opposite (cleanly destroying any event listeners etc. and returning to static text).

I'm not sure if aloha uses events or some other mechanism to track changes (my guess is events?), but what you're doing in that code is transforming the given element if necessary, and also handling any changes so that they are mirrored by the actual model.

The select2 is an example of using events.

The rest of the code in there is mostly just providing hooks for adding callback functions.