I have not really understood when and why they are needed; I would be interested to see an alternative also because it might improve my understanding.
On Nov 9, 3:27 pm, ringemup <ringe...@gmail.com> wrote: > I don't use them either for much the same reasons, and because I often > end up using custom render_to_response shortcuts that set common > context or handle custom template loading. Although the new class- > based views may make them more customizable. > > I don't see much need for an alternative, though (I'm perfectly happy > writing my own views), and don't know what sort of alternate approach > you're suggesting. > > On Nov 8, 6:42 pm, Ted <ted.tie...@gmail.com> wrote: > > > What are their pros and cons? How often do you use them when you're > > coding? > > > The more I code in django the less I find generic views to be useful > > shortcuts (direct to template being the exception). > > > My biggest complaints are: > > * You don't end up saving many keystrokes unless you have 3 or more > > views that are going to use the same info_dict. > > * They can't be tweaked or changed much before you have to move the > > code to the views file, destroying the keystroke savings. > > * Second syntax for doing the same thing makes Django harder to > > learn. > > > Am I alone on this? > > > I've thought about it and i think there is a better way. I want to > > see if there are others in the community who aren't in love with > > generic views before I develop the alternate approach. > > > I'm not trying to start a flame war. -- 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.
