37

i finally got a chance to go through the django tutorial yesterday. initially, i’m very impressed. it doesn’t really go too deep so it will be interesting to see how it goes from here. my main concern is with deployment not being as easy as a jar with the framework and everything. it appears that installing a version of the framework is required and the application/project is separate. you can easily move applications between projects. a project in django is like a website, basically. you can then have multiple applications within the site. for example, maybe a weblog, poll, image browser. you could then, theoretically, easily transfer those to a separate non-related site. this is how the automatic admin application works. the admin app is awesome. easily generates an interface for managing all the models in the application.

my other concern is about how upgrades work. when creating an application, the model python objects are the definitive source. from those objects, the tool generates sql for your chosen database to create and access the tables. you can generate sql scripts without actually running which is nice.

i’m just going to have to dig into the documentation a bit more. they are supposedly working on a book. that’s probably why the tutorials dropped off. whoever’s writing the tutorials has a good style.

hopefully, there’s more to follow on this.

i think i’m all caught up now.

This entry was posted on Thursday, April 20th, 2006 at 22:27 and is filed under computers, eurotrip-2006. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.