> 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.
I understand. I had the tag idea too, but still it seems to me that this is putting business logic in the V of MVC - don't get me wrong, I said that Django has a beautiful architecture. This is just pondering. Thank you for this insight into the development minds --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
