The Extent of Editorial Power
The title refers to the thing that started out as the “map editor” and which still bears that name (actually, the app is called ‘Bobby’, for no reason I can remember). As I’ve added bits of functionality, and in particular as the database has become more heavily involved, the editor application has expanded into more of a “game editor”. This continued over the weekend as I added more database controls for configuring the rules applied within the game processing itself, in this case, the amounts of food that are consumed, gathered and farmed. It was one of those dull but necessary jobs that are best tackled over the course of a slow Sunday, but it did allow me to tidy a few related code sections and to employ some Python techniques that I hadn’t tried before, so although I wouldn’t rank it as a triumph, it leaves me satisfied that something was achieved.
It also became clear as I was doing it that I will need to think seriously about some form of standardised administration mechanisms to deal with the whole area of tweaking game variables on the fly without bringing the thing down around my ears. I probably also want to allow a lot of it to be done via the django administration web interface, so there’s another job for the pile.
In a minor tweak to the web-pages, I’ve changed the page access so that there’s no need to manually log in as a guest to have a look, but I still don’t fully understand what the problem with the web-cache at work was/is. I’m going to put that to one side this week and concentrate on fixing the view positioning issues with the caching switched off. At least I know then what is my code and what is the remote proxy caching.
