FWIW given my complete newbie perspective, I have a couple of reactions.
First, it is clear that the answer to my question that started this meandering thread is a resounding no. I sort of expected that would be the case, but I just wanted to be sure.
Second, there's only an advantage to adopting a particular AJAX or other JS toolkit or library into Django if it were so tightly integrated that it would make the job of using that library from within Django more seamless. But with seamlessness comes loss of control. (At the very least, it's true that trying to maintain control or the appearance of it while tightly integrating such functionality would be challenging and an unecessary diversion of resources.)
To me, the Django dev team should focus on things only they can do (i.e., core functionality and extensions to it that really have to be in the base), leaving stuff like JS lib implementation to others who see an advantage to having some level of integration.
Now that I basically understand how to implement AJAX in Django, I'm happy with the current thinking. What I wanted to avoid was a situation in which the framework I chose got in the way of implementing whatever JS or AJAX stuff I wanted. It seems clear to me that Django stays out of the path and that's where I think I like it.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Shafer, Information Product Consultant and Author
http://www.shafermedia.com
Get my book, "Revolution: Software at the Speed of Thought"
From http://www.shafermediastore.com/tech_main.html
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
