[Seaside] Re: Named PTAjax calls

Aaron Rosenzweig aaron at cocoanutstech.com
Tue Dec 17 01:25:37 UTC 2013

Oh c’mon, no takers?

Nobody has faced this before?

I can’t believe something so easy in WebObjects is so hard in Seaside. (Ok, that was below the belt). 

In WO, all I have to do is drop an “AjaxWOSubmitButton” component on the page and then bind the “functionName” binding. I can immediately call that name in Javascript from the client side and anything in the “action” binding is performed and all the form bindings are synchronized. 

e:  aaron at chatnbike.com  t:  (301) 956-2319 		

On Dec 15, 2013, at 9:50 AM, Aaron Rosenzweig <aaron at cocoanutstech.com> wrote:

> Hello,
> Is there a way to “name” a PTAjax callback so that it can be conveniently invoked from javascript?
> Situation:
> Want to effectively have a submit button (or hyperlink) on the page with an on click Updater callback… then from something programmatically on the page… *click* that link.
> Problems:
> 1) Having a hidden button or link to click is not elegant (I feel dirty)
> 2) It doesn’t always work. For various reasons, doing a domElement.click() is not the same as a human hand doing a click because it doesn’t generate a full mouse click event.
> Thought:
> There must be a way to setup the following:
> A) Create a PTAjax object with a name that is a global javascript variable on the client side (web browser)
> B) You would provide the “javascript function name” a “seaside callback” a “HTML form ID or form name” so that synchronization of form variables can take place and finally an “update container ID”
> C) You could just invoke it from your javascript code and know that it will safely update the server.
> Does this make sense?
> e:  aaron at chatnbike.com  t:  (301) 956-2319 		

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20131216/b777e382/attachment.htm

More information about the seaside mailing list