design question regarding jquery serializeForm

If I understand correctly, the jquery serializeForm method causes each
callback method for the form fields to be invoked individually.

I want to use this approach because I have a small form at the top of
a big scrolling list of data, like the activity stream in facebook,
and I want to submit the form without reloading the entire page.

What is the best way to commit the data in the form?  If I create a
server side commit method, can it be invoked safely via a callback
from the ajax onSuccess: code?

Thanks for the guidance.

Larry
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On 17 October 2011 17:16, Larry White <[hidden email]> wrote:
> If I understand correctly, the jquery serializeForm method causes each
> callback method for the form fields to be invoked individually.

Yes, with the exception of those on form buttons (it wouldn't know
which one, and triggering all of them wouldn't make sense).

> What is the best way to commit the data in the form?  If I create a
> server side commit method, can it be invoked safely via a callback
> from the ajax onSuccess: code?

Not sure what you mean by server side commit method. What you do do is
essentially have a normal form somewhere on your page with an ID that
you know. Then you can trigger its callbacks from any event.

Lukas

--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside