most javascript frameworks have a way to stop to propagation of an
event - say when you click a link.
jQuery: Event.stopImmidiatePropigation()
MooTools: Event.stop()
Both of them i think( i know mootools does ) have a way of dealing
with patterns of selectors. say all of the links have an ID that
starts with ajaxform-
So you can easily grab all of the links of this type and attach events
to them.
So, you could have the links on the page have a hard coded link or a
link via the {% url %} tag link to the plain old vanilla form.
In your javascript attach a click event to the links that does the
ajax - say your script calls the view function and returns a block of
HTML or some JSON data you can deal with. And you can do what you want
with it.
If the user's javascript is turned off - the AJAX never happens and
the link to the plain vanilla form will work as normal.
django requests have the is_ajax() method so you shouldn't need to
write two separate view functions for this although you could.
On May 6, 8:27 am, Chris Dew <cms...@googlemail.com> wrote:
> I'd like to develop a Django application with the following
> properties:
>
> A page (list of items) will have a link to a page with a form to add a
> new item.
>
> If there is no javascript, the link will take the user to the new page
> and let the user submit the form, then return them to the initial page
> when the form successfully validates.
>
> If there is javascript, the link will open the form *within* the
> current page (via ajax, perhaps as thickbox or greybox). Submission/
> validation errors of/on the form will take place entirely within the
> current page. When the for is submitted and valid, the form's div
> will disappear/close.
>
> At the moment, I think that I need to have ajax and non-ajax views for
> *each form* within the application.
>
> I also need to code form template snippets (for ajax) for *each form*
> which are included by the templates for the non-ajax pages.
>
> Has anyone developed a Django extension which makes this easier - some
> form of 'unajax for non javascript-capable browsers'.
>
> I realise that I'll probably need to do this myself, by hand, but I
> thought I'd ask the question, just in case.
>
> Thanks,
>
> Chris.
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
