Hi, I've followed your discussion only in parts. But I usually handle everything that is outside of the scope of the normal generic views inside the manipulator, and I have patched some generic views so that they accept a manipulator instance as additional parameter. (see ticket 1563 for patch). I call the generic view from the view function.
This makes a nice general pattern. You get very short view functions, the manipulator concentrates on the "real stuff", and the generic view handles all the GET/POST/validation logic, that tends to be the same for most views. Michael --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
