watchlala at hotmail.com
Thu Jun 16 18:51:03 UTC 2011
I think you can return a component or something with #answer: if I'm not mistaken. There's always WATask, which may fit your idea.
Otherwise, you may consider using announcements. Maybe do form authentication with ajax and return any errors, or even return the results via ajax.
Just some ideas,
> Date: Thu, 16 Jun 2011 17:50:08 +0200
> From: milan.mimica at gmail.com
> To: seaside at lists.squeakfoundation.org
> Subject: Re: [Seaside] flow
> Julian Fitzell wrote:
> > but I'd question why you were using #call:/#answer: at all.
> > If the #answer is in response to a #show: or is triggering an
> > #onAnswer: block in an embedded component, it should work fine to
> > #answer inside the #respond: block.
> Well, it's quite simple. I'm #call-ing a component which does a ticket
> reservation. After the user fills the form, in the callback of the OK
> button, I'm sending a PDF (the ticket) to the user and returning flow to
> the calling component. That's how I imagined it anyway.
> Milan Mimica
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside