<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>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.<br><br>Otherwise, you may consider using announcements. Maybe do form authentication with ajax and return any errors, or even return the results via ajax.<br><br>Just some ideas,<br>RS<br><br>> Date: Thu, 16 Jun 2011 17:50:08 +0200<br>> From: milan.mimica@gmail.com<br>> To: seaside@lists.squeakfoundation.org<br>> Subject: Re: [Seaside] flow<br>> <br>> Julian Fitzell wrote:<br>> > but I'd question why you were using #call:/#answer: at all.<br>> ><br>> > If the #answer is in response to a #show: or is triggering an <br>> > #onAnswer: block in an embedded component, it should work fine to <br>> > #answer inside the #respond: block.<br>> <br>> Well, it's quite simple. I'm #call-ing a component which does a ticket <br>> reservation. After the user fills the form, in the callback of the OK <br>> button, I'm sending a PDF (the ticket) to the user and returning flow to <br>> the calling component. That's how I imagined it anyway.<br>> <br>> -- <br>> Milan Mimica<br>> http://sparklet.sf.net<br>> <br>> _______________________________________________<br>> seaside mailing list<br>> seaside@lists.squeakfoundation.org<br>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside<br> </div></body>
</html>