Use separate message collections for each thread to facilitate lookup and lazy loading
Fix whitespace, lint
Let thread collection double as contacts db

When a thread is 'destroyed' from the UI we delete its messages and mark
the thread as inactive, (in other words, keep it around as contact info).
Additionally, we only load active threads when initializing the UI, and
reactivate threads when new messages are added to them.

Conflicts:
	js/models/messages.js
	js/models/threads.js
	js/views/conversations/show.js
Condense some code using Backbone.View's event framework
Use mustache template for message rendering
Use $.find so these locals can go away
Rename file
Don't make a new collection on every call to thread.messages()
New layout/design

Two column layout and style tweaks. Templatized conversation views.
Generalized list view.
Move ui init out of nacl callback and remove some lines that no longer apply
Make header and footer/form work without overflowing
Cull dead code

Most of this no longer needed because of templating and list views.
Let list view changes the color of selected conversations
Parse the template before binding render to an event
Refactor conversation view into two classes

One that resides in the left hand column as a list item, and another
which displays in the main column and handles ui events therein.
Remove old convo compose view
rm stale css
Don't reopen a currently selected conversation
Close an open conversation before opening another
Don't recreate views unnecessarily

Let ConversationListItemView save a reference to its corresponding
ConversationView. This lets it render or delegate/undelegate events
when opening and closing a conversation.

Similarly for ConversationView itself, which contains a MessageListView.