On Fri, 2008-03-07 at 13:18 -0800, [EMAIL PROTECTED] wrote: > +1 > > And I think that an equally important point here is not necessarily > that people can subclass an existing generic view, but that they can > subclass BaseView for an easier way to create their own generic > views. Anything which makes good practices for reusable apps easier > is a win in my book. > > About the bikeshed, I might paint it "finish", although I think that > post_save isn't such a bad name either.
So that we're clear: my problem with post_save is that it isn't at all self-explanatory. It tells you when the function runs, not what it does. It's good friends with functions called sometimes(), on_every_request() and only_when_necessary(). A function's name should give you some hints as to the utility of the function. So something like construct_response(), since it's actually a hook for providing tweaking after the main action has run when you want to control the response -- the one thing that's hard with generic views at the moment. Regards, Malcolm -- I've got a mind like a... a... what's that thing called? http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
