[Seaside] Using updater without triggering action callback?

Boris Popov boris at deepcovelabs.com
Thu Aug 23 21:30:42 UTC 2007


That was my first reaction as well and I did try to suppressing the
callback from the inside, however it's really the render notification
signal that immediately follows that will screw things up even if I
don't actually do anything in the callback itself as demonstrated by my
later suggestion of adding an empty callback to SUFormTest to be able to
see the mayhem. It seems there should be a general solution to this and
the more I think about it the more I lean towards trying to suppress
execution of that single callback altogether to see if that fixes the
problem but I can't think of a clean way of tagging it as such quite



DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com


This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Lukas Renggli
> Sent: Thursday, August 23, 2007 2:26 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Using updater without triggering action
> > Simply because search criteria form includes a number of fields and
> > submitting half of it would do no good for actually executing a
> > with only half the query parameters set later on. Or say you only
have a
> > single select list + button on a form, and you'd like it to have
> > action. This is a bug IMHO, not a feature.
> The easiest solution for your problem would be to write in your
> default action block something like:
>      self session currentRequest isXmlHttpRequest
>           ifFalse: [ " default action code " ]
> I am not really sure if we want this as a default. There are several
> problem serializing hidden-fields, buttons and some of the "composed
> form elements" like checkboxes and multi-select lists (some of these
> problems have been fixed in 2.8).
> Maybe you could also trigger in your drop-down just the relevant form
> elements using a cascade of #triggerFormElement:. Note this also works
> for multiple forms, etc.
> Lukas
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list