Class Based Views let you override and subclass views to modify their behavior, I find them to be very quick once you get the hang of them.
On Wednesday, September 14, 2011 at 9:33 AM, Kurtis wrote: > Hey Guys, > > I'm relatively new to Django 1.3. As others have noticed, there is > less documentation around the Class-Based views than typical for > Django. No needs for apologies as I have seen in other threads. I > don't blame others for my lack of knowledge :) > > If I am working on a large project from scratch, would it be smart to > just use the traditional, function/method-based views? Or should I go > ahead and try to adapt the class-based views? I am working on a > deadline so the amount of time burnt searching more in-depth for my > answers could be a problem. On the other hand, if there are any > advantages to using Class-based views, I may want to take advantage of > them. Unfortunately, I don't know enough about the Class-based views > to really weigh that out on my own. Any information regarding this > decision would be greatly appreciated. > > Thanks! > -Kurtis Mullins > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" group. 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-users?hl=en.
