add signup view

doesn't actually talk to the server yet
signup modal error display

no client-side validation yet, and the server just returns a 404. next
step is to make the player create api work.
add player signup

when signup is successful, initiate a session and show the game view. when
it fails, show errors inline.

add an alert subview to the game view so we can show alerts like "thanks for
signing up".

add better error handling for the api, returning a jsend error rather than
an ajax error.
use am serializer to serialize player
normalize player attributes
stop using dynamic templates

for all the reasons enumerated in
http://robots.thoughtbot.com/post/45495314926/backbone-js-templates-without-logic-or-interpolation
extract view templates into html files

use require.js text plugin to load templates
add character selector and character creation

redefines the logout action to simply exit the world and go back to
the character selection screen. eventually there will be a quit option
to end the session altogether.
make sure login view is removed correctly
add quit option
only show logout control when game is in session
rework session management and character selection saving

session is wholly based on player state now. session id is set from player
token. synthesizing player state on the client side for now but will get it
from the server after login in the next revision.

save character selection in the session. not yet locally stored so it
does not persist across page refreshes.
get player attributes from the server

move local storage logic from session to session manager
serialize session token in camel case
persist selected character in local storage

forces some session lifecycle updates to correctly save and remove the
character info in local storage. move the meat of log out and quit event
handling logic from the router to the account nav view where it belongs.
character selection
use subview for character selection
add character name to game view
send enter world message upon connecting to the server

display a system chat message when the world is entered. add timestamps
to messages.
add simple command handling to world server

disentangle the concepts of "commands" (sent from a client to the server)
and "messages" (sent from the server to a client). a command is processed
on the server and may result in zero or more messages sent to zero or more
clients representing different players.