On Fri, 2008-02-15 at 02:37 -0800, dreamingbear wrote: > While studying Django (yes, I'm a newbie) and being dutifully > impressed by the beauty and coherence of the general architecture of > the whole thing, I found myself wondering this question: > > Why template context processors are passes a request object instead of > the context itself. > > As I see it, having the context available would allow the processor to > do all sort of wonderful things, building upon previous processors > results, like changing the context (e.g. modifying fields content) > depending on the current user, or adding new, calculated fields > altogether, in a word to accomplish business logic. I understand that > this can be done in views, but what if you want to apply the same > logic to *all* views? Isn't this the DRY principle?
You don't need this extra functionality because you can already do it. Just use normal programming techniques and factor out the common stuff. To wit ... In one project I'm working on at the moment, there's some stuff I need to do in every view for a particular cluster of views. So instead of calling render_to_response(), I call my own function finish_view(), which does this common post-processing and then renders the template. It's no more typing than normal. That fits in well with Python's "explicit is better than implicit, too". It's very clear to anybody reading this code that there's some (common) extra stuff going on at the end of evrey method. Or you can put a tag into the base template used by all these views that does this processing. It will have full access to the context. We don't want to have multiple ways to do the same thing and try fairly hard to keep the different processing levels separate, backed up by a healthy dose of experience about how things tend to pan out in practice. Regards, Malcolm -- No one is listening until you make a mistake. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
