<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'>Mayhaps embedding it? It would be easy enough for the user to download then.<br><br>RS<br><br><hr>From: jfitzell@gmail.com<br>Date: Thu, 16 Jun 2011 23:43:31 +0100<br>Subject: Re: [Seaside] flow<br>To: seaside@lists.squeakfoundation.org<br><br>On Thu, Jun 16, 2011 at 4:50 PM, Milan Mimica <span dir=ltr><<a href="mailto:milan.mimica@gmail.com">milan.mimica@gmail.com</a>></span> wrote:<br><div class="ecxgmail_quote"><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex">
<div class=ecxim>Julian Fitzell wrote:<br>
<blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex">
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 #onAnswer: block in an embedded component, it should work fine to #answer inside the #respond: block.<br>
</blockquote>
<br></div>
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.</blockquote>
<div><br>But how can the user both download a file *and* see an HTML page displayed? You can only respond once to a request...<br><br>Julian<br></div></div>
<br>_______________________________________________
seaside mailing list
seaside@lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside </div></body>
</html>