On 11/14/05, Eugene Lazutkin <[EMAIL PROTECTED]> wrote: > I don't recall anybody proposing "AJAX in the core".
I've seen it asked for more than once, particularly in the IRC channel. People ask for Django to pick one AJAX library and integrate it. To me, that's "AJAX in the core". > While Ajax is generating a lot of buzz lately causing adverse reaction in > non-marketing > people, don't overlook it is potential to improve usability of web sites. I don't feel that I am; I do feel that right now the vast majority of people who are clamoring for AJAX are woefully uninformed about what it is, what it does, and how best to use it. As a result, it ends up not being used to enhance usability, but rather to provide lots of flashy effects and transitions which may well have a negative impact on overall usability -- many people are rushing to "AJAX-ify" their applications without doing any sort of thinking about usability at all, let alone testing to determine the impact. Which, again, says to me that the best thing for Django is to let all those people be Some Other Framework's Problem. > As any indication of that you can look at requests in this list and in > Django-User for reuse of parts of Admin in their own applications. People > don't want to reinvent the wheel, they want to reuse the wheel. Same goes > for Ajax. Integrating AJAX into Django would mean settling on one toolkit to use for AJAX effects, and building around that. This is inconsistent with how Django handles other things, because for the most part Django is agnostic about what tools you use; for example, if you don't like the template system, you can use another. But this sort of flexibility isn't easy (or, sometimes, even possible) to maintain with AJAX toolkits. -- "May the forces of evil become confused on the way to your house." -- George Carlin
