Today I spent several (read: about 4) hours working with and toying with a neat little web application framework called Django. It’s very much like working with Ruby on Rails, but a little bit more intuitive.
The downside is the documentation is only slightly poorer than Ruby on Rails’ documentation, which is to say, not very good. The tutorial helped quite a bit with the basics, but even that does not work “out of the box“.
I’ll keep working on it, as I’m interested to see if I can whip up an AJAX implementation for it, making data entry web applications easy to put together.
That’s right, in a matter of a few hours, I can build you a character database, fanboy!
Posted in AJAX, Django, Game, Neat |
Hey, thanks for checking out Django. We’re working on the documentation as our main goal before our first “official” release.
Which part didn’t work out of the box for you?
Well, when I went through the steps in the tutorials, I had some problems getting the design rewrite to work properly, at least, that’s my guess.
I tried to put in /polls/1 to see the poll, and it threw up at me. So I tried a random number, and it threw the same thing at me. Error404.
It worked before uncoupled the polls application, but not after. I looked and looked and could not figure out what was causing it.
I didn’t mean to make it look like I was displeased with Django, I’m more frustrated that it didn’t work as I expected.
I’d like to see some documentation on getting it to work without mod_python and with Apache (1.3), however. I had some issues testing it initially, and turned on threads in Python, and it worked. Do I just need threads for the django-admin.py runserver command?