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 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 -~----------~----~----~----~------~----~------~--~---
