On Dec 5, 6:37 pm, Reinout van Rees <rein...@vanrees.org> wrote:> That link will expire in a month, so that's not really suited to posting> on a mailinglist that people might still read a month from now. You're right. Here is another link: http://pastebin.com/w7u74AJ7 On Dec 5, 4:07 pm, sebastien piquemal <seb...@gmail.com> wrote: > Could you post a link to a place where class-based views are being > criticized ? And also in what sense are they convoluted ?
I chanced on many places, on the list, in the issues, and over the web, where people expressed confusion over the current design of class- based views. Here is one such place: https://code.djangoproject.com/ticket/13879 This ticket documents a missing feature (the issue of decorators with arguments I outlined in my first post) but the current state is so convoluted that it was left marked as Design decision needed, for lack of a clear way out of the mess. The complexity is inherent in the design decision that was made about class-based views. I won't go into detail here, because I still need to read up the references on the link posted by Russell. But it seems the design that was chosen violates at least one of the original requirements, "Ease of decoration." I believe my design (which is basically this https://code.djangoproject.com/wiki/ClassBasedViews#__new__ ) is the correct solution, but I'll make sure to review past discussions and post a better argument when I'm ready, including an implementation passing the current test case. The devil must be in the details. Tobia -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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.
