Hello everybody, Thank you for your feedback. And pretty soon I will tackle this problem in an external app - or consider joining the party if somebody else has started, in this case feel free to let me know.
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. I just fail to see the difference, it would be great if someone could explain that ! Thanks for your feedback. -- 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.
