Picking up loose ends: Position Pieces

2008-11-17T00:00:00-08:00

I'm picking up a pet project of mine that I was working on a few months back. It's written in Django and is openID enabled... but I didn't used django openID and I have no clue why... I wrote my own code.

My best guess is I wrote my own code, just so I could understand it better, and that perhaps django openID wasn't mature enough or documented well enough.

Whatever the reason, in the future when I take the non obvious route... that I actually document the "why?" This will save me the tedious task of determining if I need to swap out my code and replace it with something that's more maintained.

In any case, it's certainly refreshing to tool around with Django some more... it's a lot more pleasant than the PHP that I'm often subjected to...

reusability

2008-01-30T00:00:00-08:00

[tags]django, plugins, apps, projects, symfony[/tags]

A project is a collection of settings for an instance of Django, including database configuration, Django-specific options, and application-specific settings.

The Django Book, Chapter 2:

A few people have been asking for more comparisons between symfony and Django. For me it's a great way of understanding Django and python as well as symfony and PHP.

Reusability is at the core of Django, not an afterthought. The only unique part of an app is the settings and the views. Everything else is an application that can exist independently of your app. It's nice and decoupled.

This wouldn't be impossible to do in symfony. Each module could be designed from the start as a plugin. Complete with its own set of models and default templates. The configuration of a project/app could then make the web app unique.

Right now the bulk of my symfony models are tightly coupled to their apps. It's a little confusing, but there isn't a direct correlation between Django projects, Django apps and symfony Projects, apps and modules. Each kind of overlaps one another.

Dave Dash

Picking up loose ends: Position Pieces

reusability