The first article of an eight article series on using Django to create apps that exist simultaneously as independent web applications and as Facebook applications. This segment covers putting together our development setup.
When I develop with Django I'm constantly searching documentation, trying to figure out new modules and generally looking for answers to new problems as they arise. Today I'm introducing a new project, Findjango, which hopes to being a valuable resource for searching on Django-related topics.
I've been working on a Facebook application with a couple of friends recently. We decided to use PyFacebook library, but there was a brief period of intense confusion on my part about how to use the PyFacebook library without the included middleware. I worked through it, though, and this article has some advice on how you can do the same.
A look at how to manage deployment complexity with Django using Fabric. Something of a continuation on the post from yesterday.
Moving along in the Two-Faced-Django series, we look at using JQuery for Ajax in the webapp portion of our program.
The seventh (and final!) entry in the Two-Faced Django series. We look at implementing Ajax functionality in the Facebook app we have been developing with PyFacebook.
Luke and I competed in DjangoDash a few weeks ago, and hey, we actually finished a site.
The second example in the Loose Coupling in Django series. This one looks at a place where Django's loose coupling is at its tightest: the Django ORM.
A rather rough and tumble walkthrough for using Django and JQuery to make autocomplete input fields.
Software engineer, technical leader, sci-fi reader, and so on. Born in NC, living in SF, and glad to grab a coffee.