Back when I was initially designing Atlarius, I toyed with the idea of using Django to create it. In fact, I went so far as to begin to describe the data models using Django’s system. I found, however, that a limitation in the way I could describe the models caused me an issue at the very start. I forget exactly what it was, but though I probably could have found a way around the problem it caused me to think “If I have already hit a problem, should I take the chance of encountering ones with no solutions later in the project?” So, I scrapped the idea and went with PHP.
However, recently I have found myself applying for a developer position involving Django. For this reason, I decided to take a closer look at Django. In a few easy steps, I created myself a simple blogging system allowing user comments (screenshots here and here). I was quite impressed by how easily the administration module and HTML forms were created with Django.
So, here I am, both impressed by Django and wanting to learn more about it. I am considering using Django to create a simple version of the Atlarius engine and see how difficult it is. On the other hand, that seems like such wasted effort. I’ll have to see if I can think of another useful project to create with Django. Or perhaps a worthwhile project to contribute to. Decisions, decisions.
I was having a hard time deciding between simply not allowing comments, requiring an e-mail address and needing approval, or requiring registration on my site. I didn’t like these options. The first seemed a bit anti-social, so I didn’t want that. The second seemed to require effort on my part, and I don’t want that. The third seemed to require too much of an investment from anyone who wished to leave a comment. I’m not quite so conceited as to think that most people will think my blog is worth reading, let alone registering for.
Yet I found a solution. I installed the OpenID plugin for WordPress, the code which powers my blog (as I’m sure you can tell). Now anyone who wishes to login to my blog using their own OpenID provider they can do so, and it will automatically approve your comments. Users who don’t have an OpenID can still register normally, or comment by putting in an e-mail address, but will require approval on their comments. It is the best solution I can find that is fair to both (potential) commenters and myself.
I see now, as I checked while writing this, that my friend Denver over at OSS Guy has this plug-in installed already. I should have known. He always seems to be on the ball with that sort of thing. 
Hoo-rah. The developer said, “Let there be a devlog.” And then there was a devlog. Far stretching is the developer’s power.
Ok, enough of the nonsense (for now). People are constantly telling me to sign up for Facebook, Twitter, etc etc ad infinitum. This blog is my response to that.
As of today, I am nearing completion of the database design and the ticker’s functional specifications for my browser-based MMORPG. I should be able to start coding tonight or tomorrow, which is an exciting step. I’m sure all you developers can relate: Planning isn’t as fun as coding. I am starting to have it sink in now exactly how many details complex programs need to keep track of and control. I’m planning to write the ticking engine in C++, whereas the user interface will be AJAX created with Pyjamas. I am also considering using Django as the back end for the web content, though I have not used it before and will have to look further into it.
Well, back to planning.
