Inline. "Baishampayan Ghose" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Heh, AJAX, as you might have noticed is mostly all buzzword crap, but
No. My experience is quite opposite: AJAX is very useful tool. Not more, not less. > again many not-so-knowledgeable developers would choose a framework > purely on the basis of buzzword-compliance. I don't have any problem with that. If that's their criteria --- God speed. > Django to be buzzword compliant too? None can deny its importance in > today's world ;) Why is it important for Django? >> 4) Let's return to the topic and discuss it in constructive manner. While >> you chided me I actually tried it (see my other post). > Yeah, but that was in a different thread, and I thought it was good to > stop THIS thread. ...especially when it was stopped already. :-) > Yeah surely. I have discussed about this AJAX stuff at length on IRC and I found < 10 relevant lines from you on 11/15, which were a little bit vague. Probably you discussed it some other day. Could you share what exactly should be added to Django? I understood you favored Dojo Browser I/O profile. I didn't understand what kind of Django additions are required to "provide a loosely coupled basic XHR framework". It would be great, if you have some ideas on that. > third party AJAX library. But what I want in 1.0 is a loosely coupled, > minimal AJAX library + API which in one hand will enable the developer It would be awesome, if somebody can sketch this API. > to do some XHR stuff fairly easily and also on the other hand won't stop > him from using another full blown library if he wishes. Correct me if I > am wrong, may be what I said is not much ``buzzword compliant''. :) It all depends on details of your proposal --- you can go either way. ;-) Thanks, Eugene
