This looks cool Alexandru. What I can see it really leverage the capability of generic views. I hate repeating too. And your solution seems to be very elegant. Going to test it out.
On Mon, Jul 27, 2009 at 4:51 PM, Alexandru Nedelcu <a...@lexoft.eu> wrote: > > On Mon, Jul 27, 2009 at 2:55 AM, Alexandru Nedelcu<a...@lexoft.eu> wrote: > > I do miss a feature from Catalyst ... chained actions. > > I added this functionality to Django by myself (just a few hours > > hack), see here (example + code): > > http://code.google.com/p/django-catalyst/ > > I updated the examples on that page to make the purpose clearer ... > http://code.google.com/p/django-catalyst/ > > I would be interested to know ... > 1) what are the similar techniques in django to cope with reusable > parts when processing requests ... I know of context processors, > generic views, middleware > * the problem with middleware is that it is executed for every > request, and I couldn't find a way to make that "local" to an app > (besides checking which view is executed, in process_view) > * context processors have to be manually specified if you want > locality ... I don't really like that syntax, is there any other way? > * generic views are useful, but they are executed generally > after your main view (on return) > 2) is anyone interested in this? > > Thanks, > -- http://blog.scrum8.com http://twitter.com/scrum8 --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
