Updating for Django 1.4

The Django 1.4 database config in settings.py is different (multiple
possible DBs, and the engine string contains django.db.backends), so have
changed it to work with 1.4.
Rolling back to just Maelstrom char/player info

I know I said I wanted to make this work for multiple systems, but I want to
get *something* done to start with. Simplifying the scope, going back to
just implementing Maelstrom-style character and player info.
Some more fixes to update to Django 1.4

STATIC_URL and TEMPLATE_LOADERS needed fixing in settings.py, as did admin
URL registering in urls.py.
Registered Player in admin, rebuilt DB

Hadn't rebuilt the DB since changing the Player and Character models, so
needed to rebuild those to get admin working for them. Also added superuser
for doing more admin work.

Old test skills are still around, but at this point I could replace them
with real Mael skills given that the campaign has finished.
Remove .swp files in /downtime

Not sure why they were there but they aren't anymore.
Added downtime app to admin, also added South

Downtime app is now registered with admin.

Also, I've installed South and done initial migrations for character,
downtime and skills apps. This is a good project to experiment with South on
so I'll see how it goes.
Added admin.py for downtime app, and new models

character/admin.py shouldn't have admin registration for the downtime app,
so moved that bit of code. Also added DowntimePeriod model - each (generally
90 day) season is its own period of downtime, in which a certain amount of
actions can happen. DowntimeActions are association with a DowntimePeriod
and with a character.

Oh, and South migrations for those changes, which will be going in with any
model changes from now on.

This is the bare bones of downtime. Next I think I'll see about more
character options, then sorting out skills, along with some fixtures as I
start needing test data.
Another Django 1.4 fix (MessageMiddleware)

See https://code.djangoproject.com/ticket/18018#comment:9 for the issue -
Django 1.4's settings.py needs an extra line in MIDDLEWARE_CLASSES.
__unicode__() method for Player

Also changed the Character method to match. They're now "name (PID or CID)".
Added test player

Predictably called "Bluebottle". Tried adding a character, but currently
Player.skills can't be empty. I don't have any skills added yet, so now is
as good a time as any to add some so I can mess with starting skills.

(It will be alchemy skills because that's what my Mael character had.)
Test data fixtures for chars and skills

Added initial_data.json fixtures for character and skills apps. Also made
Skill.prereqs blankable, because there may be skills without any prereqs at
all that anyone can learn.

(Technically, Alchemical Lore wasn't one of these - you needed to be taught,
or take it at chargen, or learn it from an item. But things like Navigator,
Explorer and Staunch Wounds are like this.)
Fixed issue with user_character_list() view

request needs to be the first argument of the view function:
http://stackoverflow.com/questions/13544504/django-form-got-multiple-values-for-keyword-argument

Also changed character/views.py views to use render_to_response as I'm not
doing anything other than default stuff with the template and context
objects.
URLs in urls.py now all work

As do the URLs on the template in character.views.index.

There aren't any skills in the Study Options list for my test character yet,
because it has all of the existing skills. Time to add some more alchemy
skills!
Added some more test skills

The rest of the basic alchemicals are in. Text is the "you know this skill"
description from Maelstrom, except for Mordant Purgative which I never got
before I stopped attending events.