IMC/Comsys Stuffs

[Greg Taylor]

For those not watching the commit log, you're going to want to syncdb
to get the latest changes to the com system. This will have the affect
of nuking your channel list, so make sure you either write down or
remember your channels before hand. You may @ccreate them again once
you're started back up.

The big deal with all of this is that src/objects/models.py has been
cleaned up a good bit, a few import oddities have been resolved, and
the CommChannel/Message models are now under a 'channels' app.

Even bigger, perhaps, is that IMC2 now sends and receives in a pretty
slick way. You @ccreate a channel, then create an IMC2ChannelMapping
object that links the IMC2 channel name to the in-game channel. Any
messages sent over the channel are piped out to IMC, and any messages
received whose target channel has a mapping are sent to the
appropriate local channel. This makes IMC2 communications appear just
like regular in-game chatter. The only difference is that IMC2
messages have a sender@origin style name instead of a plain character
name.

Who knows, maybe I'll get around to finishing up the comm system now
that I have something to play with on it!

Documentation will be forthcoming for IMC once I finish implementing
the rest of the specification. It'll be a while, but this is a fun
break for me from mundane codebase stuff, even if it doesn't see much
use in the future.