I see 2 solutions: 1) A manipulator and view function for each form. A URL mapping to the view function.
Advantage: Some work done for me. Unresolved: - The form response handling will be duplicated across each manipulator. - Not sure how to pull user response data back into the form if they navigate to it again. 2) Use raw request data and draw forms in template by tying Question/Options to Page model. Advantage: Code to draw forms and handle responses in one place Unresolved: - Where to put generic form response handling? I can name the form names in a way that any request can catch POST data and know where it needs to be saved. Is there a generic place to put a request.POST handling across all pages? If I got anything in the above wrong I'd be pleased to hear about it. :) Thanks, Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
