On 11/14/05, hugo <[EMAIL PROTECTED]> wrote: > Actually the only thing I can think of that would be good if django had > it, would be a REST style API to access model stuff that automatically > will be returned in JSON format. That would allow JavaScript code to do > easy database queries without requiring the programmer to write those > views himself.
+1, solves the problem at hand and possibly other future problems we don't know about yet ;) > Most AJAX stuff is just stuff built on database queries anyway (like > the google suggest feature nowadays seen as lifesearch in projects - > just a query directly run from JavaScript). Yup. And most of what the various "AJAX libraries" do isn't actually the meat of "AJAX"; rather, they provid reusable, easily-combined effects like drag-and-drop, animated show/hide, etc. Which means that, if Django just implements an API, users can go with whichever "AJAX library" best suits their particular application's needs. As for the related topic of AJAX in the admin, I think the problem of "Django bundles an AJAX library, I should use that one" can be avoided with some care in how AJAX is used within Django; if only a particular subset of functions is needed, it may be possible to bundle a stripped-down library which only includes those "AJAX components" that are actually being used. -- "May the forces of evil become confused on the way to your house." -- George Carlin
