tanis.us

As you can see, I have a weak little archive implementation up as of now. I was unfortunately led on a bit of a goose chase.

You see, my original inclination was to simply implement the archive programmatically (for lack of a better term) in the view for my root page. After a few lines of code I figured, Django has got to have a neat little automagic way to do this; just like with comments. After consulting a few different sources it seemed that generic views were the recommended solution. After creating generics for the year/month/day archives ...

I believe I have the last few kinks worked out. Although I've already had experience with mod_wsgi, I always like to have documentation to refer back to. Considering the overall quality of Django documentation as a whole I've had little to complain about, but I find the relatively poor state of wsgi/django documentation a little odd.

The documentation at http://code.djangoproject.com/wiki/django_apache_and_mod_wsgi as an example is unnecessarily complex, seems to contain a lot of redundant and inexplicable configuration, and doesn't even touch on certain optimizations that seem necessary even on a low traffic ...

I put tTwistedMud, my implementation of a MUD written in Python, on BitBucket. Since I've last posted about it, I've done some work on the underlying object model and basic game mechanics. Most notably I've begun working on player professions as well as computer-controlled NPCs. Still a lot of work to be done. I haven't yet updated the public code base with the changes to professions, but I will do so soon.

The project, as it is, can be found at: tTwistedMud