On 4/10/07, Steve Bergman <[EMAIL PROTECTED]> wrote: > Even after the developer decides upon a javascript library to use, > there is still a lot of boilerplate involved to do common things like > populating one widget based upon what the user selects in another > widget. I often need to populate one widget based upon what the user > selects in another. Or update the contents of one div without > reloading the whole page.
Again, it's not terribly hard to write views which return JSON or XML; integration with form widgets, etc. requires binding to a specific JS library or rolling our own, and that's not going to happen. Search the archive of the Django mailing lists for some of the many times this has been discussed if you'd like to learn more. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
