On Fri, Jun 1, 2012 at 12:04 PM, Michael <newmani...@gmail.com> wrote:
> I am not ready to judge right now wether they are a good idea or not. > > I can completely agree that documentation makes the views more difficult > then they actually are. Every time I create a new view, I find myself going > to the source. I think this is a case where the learning curve initially is > a little steeper so better examples and best-practices will really help > with people's implementation and also this discussion. > > This is the real issue. The docs. I'm trying to use CBVs exclusively in my latest project. I end up in the source most of the time. It might be good to start people out with very basic CBVs and make the docs much more of a tutorial. > I have been wanting to write up documentation every time I go to the > source, but sadly haven't had the time. Maybe I will soon. > > > > > > On Fri, Jun 1, 2012 at 12:35 PM, Donald Stufft <donald.stu...@gmail.com>wrote: > >> I tend to agree, in general, with the reply that there should be a >> function based api >> to cover the 80% use case, but in the case of Django's CBV's this is >> likely >> covered by the as_view method. >> >> On Friday, June 1, 2012 at 10:54 AM, Jacob Kaplan-Moss wrote: >> >> On Fri, Jun 1, 2012 at 10:14 AM, Victor Hooi <victorh...@gmail.com> >> wrote: >> >> The reason for my post - is there anything from the Django core as a whole >> on this? What's the future roadmap like in terms of CBV's? Are there going >> to be any changes to it, or are we safe to assume things will be as they >> are >> now. >> >> >> I think as a whole we're.... divided. Luke's opinions differ from >> mine, and it's entirely unclear to me who's "right" or even if there's >> a "right" to be had. And that's just the two of us! >> >> I think this might be a situation where we need some more feedback >> from the community and some more time to decide what the right move >> here is. >> >> So... what do *you* think? >> >> Jacob >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To post to this group, send email to django-developers@googlegroups.com. >> To unsubscribe from this group, send email to >> django-developers+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/django-developers?hl=en. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To post to this group, send email to django-developers@googlegroups.com. >> To unsubscribe from this group, send email to >> django-developers+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/django-developers?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
