On Sat, 2006-06-03 at 02:29 +0000, Jaroslaw Zabiello wrote: > I have heard that in Django 0.92 we will have added Ajax. We are having > 0.95 now (svn) and still nothing was added. :( > > Why? The idea is simple. Ajax is pain in ass if we would like to use > only pure JavaScript. So we need good helpers fo more comfortable work. > For me Rails has very cool Ajax support. They have even special > templates (rjs) for Ajax. It is very cool. But, the point is, that we > do no need to create it from scratch. Why? Because there is already > existing nice implementations of those helpers in Python! Another > pythonic framework - Pylons - is using it. Look at > http://pylonshq.com/WebHelpers/module-index.html. Why not to add these > libraries to Django? Why somebody would like to reinvent the wheel?
So I had a look at this. Got confused. Looked again. Hmm.. here are a few questions I have from looking at this for 30 minutes or so (and from thinking about how XmlHttpRequest stuff might look previously): It seems like only webhelpers.rails.prototype and webhelpers.rails.srciptalicious are actually providing any kind of AJAX (XmlHttpRequest) support, right? The tricky part of all this for Django is working out how it would be *used* in Django. What do you add to your templates, what other support is needed, ...? How can we make it reasonably easy to use? There isn't really a clear proposal floating around for what "adding AJAX to Django" really implies. Everybody has some ideas, but it hasn't crystallised completely yet. Please do correct me if I'm wrong, but the webhelpers package seems to provide a UI for creating the HTML + Javascript that provides the "AJAX" suport. And that UI that is not very Django-like as it stands, so it's probably still a couple of steps removed from being drop-in useful. We would have to put a wrapper over the top of these and, without doing an in-depth evaluation of the work, I would wonder if wrapping the Javascript libraries directly was more maintainable than wrapping a wrapper of them. And does it require pre-requisites that we already have elsewhere (e.g. does this portion of webhelpers depend on Routes, for example?). No concrete recommendations here, but I think this came across in the original email as being easier than it really is. That being said, I wouldn't mind seeing some support along these lines added to Django eventually, since it adds value in some situations. But it isn't a showstopper at the moment, I would have thought, and I would hope the core pieces would always work without requiring AJAX at the moment. None of which is ruled out by your proposal. So keep the discussion going. :-) Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
