On Saturday, November 24, 2012 9:11:17 AM UTC-8, is_null wrote: > > Hello everybody, > > > I can understand most of the points made here, expect just one, please > bare with me. Several hackers on this list stated that it has "obviously > not its place in Django". I don't understand why generic non ajax views > would have a their place in django, and ootb ajax support would not. But > I'm really curious. > > It would be great if someone could elaborate on that, because from what I > understand: > > - django has generic views, you are free to use them, you can use your > own, or you can use those that are provided by external apps, > - if django had generic views with ajax support, you would be free to use > the ajax support, or use your own, or use those that are provided by > external apps. >
One distinction is that generic views don't provide anything in the way of default templates. They help with the data pattern on the Django side, and you choose how it goes to the browser in a template. In an ajax response, the data is returned directly to the JS code in the browser. Because different JS frameworks may expect data in different arrangements - you end up coupling the generic ajax code to some expectation set by the browser JS code. More relevant to such an effort would be whether there was anything in the CBVs that stood in the way fundamentally. The current thought is that there isn't, but one couldn't be sure until there was an attempt. -Preston -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/VGMl8ei_U-gJ. 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.
