I've been developing small wikiesque app for Django recently, and since I'm a fan of human-friendly URIs I had some difficulty coming up with a DRY method for finding the primary model associated with any given view within my project. Of course, not every view is directly associated with a single model, but in most cases you can probably inspect each of your views and conclude that there is a single primary model instance which is most directly related. In this example, I'll explain the method which I've decided to use in order to take any requested URI path and rather than resolve it into a view, we will resolve it to a specific model instance. This greatly simplifies the process of creating sub-views which have access to the parent view's primary model instance.

It may sound strange, but every now and then I swing on over to Google and run a few searches for some of my wallpapers, particularly "See Hear Speak" and "Trampoline Tux" since people tend to upload those to various websites on a regular bases. I don't mind that people upload them as long as they include the proper CC license, but I stumbled across an article at The Register last night, which is certainly something new...

Merry Christmas everyone! I just wanted to show off the fancy 5x7" prints I had made...

I finished my second creeple quite a while ago but I haven't had time to post an article about it, so here it is. Casting went pretty well, although I made a couple mistakes with mixing too much plastic and ended up wasting a bit of it. I guess that's one of those things you learn by trial-and-error. Overall though, he turned out really good.

After the fairly successful creation of the first figure, I decided I'd order some molding/casting materials (silicone rubber, casting resin, all that stuff). I've never attempted working with such materials so this is my first attempt at such a thing. This article describes what I learned and how things went during the creation of the second Creeple figurine.