Hi Hedde, On Thursday, May 24, 2012 3:08:22 PM UTC+2, Hedde van der Heide wrote: > > @Florian, The other context variables should be dynamic aswell. >
No they shouldn't be made dynamic at all (none of them!) -- As Andy suggested CBV are a way better option. > I don't agree with your template logic. Django always seems to pass this > 'form' name in, which is a problem when you have a page with multiple forms > coming form django itself (for example: registration and auth). > But those two forms never end up in the same template, so there is no possibility of a clash etc, login goes to /registration/login.html, registration iteself to /registration/somethingelse.html. And if you really send them to the same template you can't use the builtin views and have to write a new view yourself either way... Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/pcVmO4x9Sv0J. 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.
