I followed this type of thinking and have a result I'm happy with. I have a view that accepts render_to_response args as well as an additional forms dict. Rather than call render_to_response, I call my custom view, which looks for results from a number of forms, processes if required, then returns a response. Anything specific to the form itself is stored in the form, so the custom view doesn't know anything about the forms.
http://dpaste.com/130000/ Thanks to everyone that pitched in. I've done a ton of useful reading trying to solve this. Also, dpaste number 130000! woohoo! On Dec 4, 10:35 pm, Heigler <lordheig...@gmail.com> wrote: > Maybe this code can help you about the approach, is just an example > based on your previous templatetag (i haven't tested > it):http://dpaste.com/129361/ > > The view isn't really generic, but i probablly would follow that > approach to solve this problem. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
