Another approach to version controlling the content in your Django database. This one looks remarkably good, at a glance. It stores revisions in the database, rather than an external version control system, and can be added to an existing project with just a few lines of code (and no modifications to your existing models). Looks very slick. I only have one question: what happens when you make a schema change to a versioned model (i.e. add/change/delete a field)? I’m going to assume this would render the versioned content unusable, but I’m not sure about that. Anyone know? Visit site »
My man Eric Holscher drops some Django and Python knowledge on your asses. A lot of good stuff, here. Check it out. Visit site »
Nathan shows you how you can use a middleware to manage different templates between two versions of a Django site (such as a desktop and mobile version) without having to run a separate mod_python/mod_wsgi configuration, thus saving you RAM. Nice. Visit site »
Kevin Fricovsky released this reusable FAQ application for Django. Perhaps even more interesting than a useful FAQ application, it’s a great example of an app that has been built to be as reusable as possible. I’m wanting to refactor Savoy to be as reusable as possible, so this is a terrific example. Good stuff, Kevin! Visit site »
James Tauber’s talk about Pinax at DjangoCon is a really great look at Django’s killer feature: reusable apps. Pinax is basically a collection of reusable apps — some of which were built for Pinax, and others which are independent of it — that allow one to put together a site very quickly (especially if your site is centered around social networking, as that’s much of what Pinax provides at this point). The basic concept is to separate bits of functionality (friend relationships, commenting, tagging, voting, registration, etc.) from what James calls the “domain object.” The domain object is what makes your site unique. For flickr, it’s photos. For Newsvine, it’s news stories. For Cork’d, it’s wine. If Pinax can provide all the non-domain object bits, all you have to do it build your domain object, and you’re set. Even if you’ve no interest in writing Django apps, it’s a good discussion of modularity and how this stuff works when it’s done right.
I was also surprised and excited to see that the approach I’ve taken with Savoy. While Savoy is more content management oriented (and Pinax is more focused on social networking), the basic structure of the two projects is very similar. Savoy has a set of third party apps it pulls in, as well as a set of “core” apps that are required. On top of that are “contrib” apps that are all optional. So, you simply install the core apps, then pick and choose which contrib apps are appropriate for your project, and you’re off to the races. I’m working to make all of these apps as reusable as possible. This is an ongiong process, and chances are the first will release won’t be as reusable as I’d like. But, pluggability will always be a primary goal. Finally, you can of course run your own apps alongside Savoy’s apps. Some apps even have hooks to integrate your own apps where appropriate (for example, the aggregator app, which runs my tumblelog, will aggregate content from any model of your choice, not just those that Savoy itself provides).
If you’re interested in building a social sort of site, or how best-of-breed reusable Django apps are built, definitely check out Pinax, and James’ talk about it. Visit site »
Some really, really nice additions and changes to both the functionality and design of my favorite browser debugging tool. Visit site »
Glen Stansberry writes on Django for NETTUTS. Nice. Django is really getting a lot of run lately! Visit site »
The latest episode of TWiD has a great interview with Leah and Mike of Pownce. If you’re interested in scaling and how a high-traffic, high-profile site run on Django, do check it out. Visit site »
I got to chat with Dmitry Baranovskiy, the creator of Raphaël, at Web Directions South, and I was impressed with both him and his work. This JavaScript library is Really Smart Stuff™. I don’t think there’s any doubt that SVG, Canvas, and VML are part of the future of web graphics, and Raphaël is making it possible to use them today. Awesome. Visit site »
Uses fancy-schmancy algorithms to figure out recommendations for things based on votes (from django-voting) and tags (from django-tagging). Looks interesting. Visit site »
Wow. Big win for jQuery. Microsoft is apparently planning to distribute the JavaScript library with Visual Studio, and make it the sort-of go-to library for .NET development. I’m still of the mind that backend development frameworks like .NET (and Django, and Rails, and Cake, and Java…) shouldn’t be in the business of “preferring” a particular front-end library, but you can’t really deny that this is a Really Big Deal™ for the jQuery project. Visit site »
One of the most useful third-party Django apps yet! Visit site »
Now that 1.0 is out the door, the Django team has put together a release process document. Looks good to me. Visit site »
Impressive-looking skin for the Django admin interface. Visit site »
Michael McCorry came to my Web Directions workshop and was kind enough to write up a mini-review on his blog. Awesome. Thanks, Michael — was great meeting you! Visit site »
E-Flo is at it again with a pair of really, really good screencasts that take you through setting up a Django project from the very beginning. He is building a real live site (a sort of Twitter clone with a twist), walking you through it from step one (you can also download then entire source of the site). The first two episodes cover getting your source control environment set up, getting Django’s settings.py file all configured, and then creating the models. Really, really good stuff here, if you’re looking to learn Django. Visit site »
The Google Blog goes LOLCAT. It’s informative, and funny, too. Visit site »
A Django custom field type which, in the background, stores and revisions its content in SVN or BRZ (more backends on the way). Haven’t tried it, but the code looks clean and the API is nice and Djangonic (new word? I like it.). Very cool stuff. I’d love to be able to store website content in version control on the fly. Visit site »
The good news about this post is that all of the reasons mentioned are either a distaste for bits you can swap out for your favorite (ORM, template language), or things that are planned for Django 1.1 (aggregate support). Well, except for the guy who complained that Django doesn’t allow him to make very much money, since he charges by the hour. :)