[Seaside] trapping post before fields are applied to an opject
Boris Popov, DeepCove Labs
boris at deepcovelabs.com
Mon Jun 20 15:09:51 UTC 2011
If you make Cancel an anchor, the form data won't even be sent back to
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Louis
Sent: Monday, June 20, 2011 11:07 AM
To: seaside at lists.squeakfoundation.org
Subject: [Seaside] trapping post before fields are applied to an opject
Is there a way to trap the return from a web page before the attributes
of an object are updated with the values from the web form? Say one has
a simple form with some fields that are connected to the attributes of
an object with #on:of: and two submit buttons, save and cancel.
Normally one would make a copy of the object so the original doesn't get
modified. The callback on the save button would replace the original
with the copy. The callback on the cancel will discard the copy.
If there is a way to see that the cancel button was clicked BEFORE the
values of the form fields are applied to the object and stop them from
being applied, one wouldn't need a copy of the original object. The
#on:of:'s could be made to the original object and would be used if the
save button is clicked and not if the cancel button is clicked.
Is there a way to do this now? If not, would it be hard to add?
Keystone Software Corp.
mailto:Lou at Keystone-Software.com http://www.Keystone-Software.com
seaside mailing list
seaside at lists.squeakfoundation.org
More information about the seaside