Hi there, IMHO I think we are discussing two different topics here. The first one is documentation. I've just added a page to the wiki outlining the actual state of the CVB docs and some ideas on how we can improve it. Please fell free to expand/object/modify/destroy what I've written. I hope that between us all we can decide which way to move forward regarding the documentation in an organized effort. At least agree as a community in how to organize the docs, so we could then have "pieces" of docs outlined to be written.
You can check it out here: https://code.djangoproject.com/wiki/ClassBasedViewsDocs The second one is the actual Generic CBV. From my point of view there's a missing GCBV which I've discussed in https://groups.google.com/d/msg/django-developers/rkh9oG603XI/By78sCl3xmsJ . Right now I'm thinking about a different approach that I've been discussing in #django-dev. A view that can handle any number of "formlike objects" (eg modelforms, formsets, inline formsets), validate and process them. This is a common problem that most projects would be able to use. Hope that with all this movement we can move this aspect of Django forward. Regards, Iván On Fri, Jun 1, 2012 at 2:36 PM, Steven Cummings <[email protected]> wrote: > The docs around the provided CBVs and mixins are an issue, but also what is > missing is that programmers seem to still think those that are provided > should work for more cases than they probably do. When the narrative for > CBVs is documented, should Django focus on mixins and state the expected > limits of the provided classes? I think people are finding those limits > pretty quickly (e.g., "I need more than one form on this page!"), and then > perhaps conclude that CBV's are "broken". Perhaps the idea that your site or > Django app may need more specific base-classes needs more promotion? > > -- > Steven > > > > On Fri, Jun 1, 2012 at 12:21 PM, Adam "Cezar" Jenkins > <[email protected]> wrote: >> >> On Fri, Jun 1, 2012 at 12:04 PM, Michael <[email protected]> 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 <[email protected]> >>> 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 <[email protected]> >>>> 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 [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. >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Django developers" 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-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 [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. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" 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-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 [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. -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
