On 11/16/05, hugo <[EMAIL PROTECTED]> wrote: > keep in mind that things should at least have lower-level APIs that > could be used even if the selected toolkit isn't used itself, but some > other toolkit is.
Again, +1. Some sort of (hopefully RESTful) API which can respond to queries and toss back a chunk of XML or JSON would be the ideal, I think. That way Django can bundle whatever ends up being preferred, but developers who don't want to use it aren't too terribly penalized because they can still build AJAX into their applications. And building an API like that probably wouldn't be too difficult; a rough version (but robust enough to do, say, the "live archives" that are popular in certain blog systems) could easily be implemented right now just by hooking generic views into templates which return the data in the appropriate format. And yes, I misspoke the other day when I referred to Protoype, but meant scriptaculous -- the latter is the one which has both AJAX functions (via Prototype) and a variety of solif visual DHTML effects. -- "May the forces of evil become confused on the way to your house." -- George Carlin
