Right, so if you open a new window or embed inside on iframe or use JS to somehow fetch and embed the content, then that will work fine since a second request/response are involved. One callback returns the PDF and the other does the #answer.<br>
<br>Julian<br><br><div class="gmail_quote">On Fri, Jun 17, 2011 at 2:32 PM, Robert Sirois <span dir="ltr"><<a href="mailto:watchlala@hotmail.com">watchlala@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div dir="ltr">
Hehe yea. I was thinking the pdf could be embedded in whatever the response page is, that way you could preserve the navigation. Am I getting at what you're thinking Milan? Some sites open up new pages for printing things, too.<div>
<br></div><div>RS<br><br><div><hr>From: <a href="mailto:jfitzell@gmail.com" target="_blank">jfitzell@gmail.com</a><br>Date: Fri, 17 Jun 2011 08:46:07 +0100<div class="im"><br>Subject: Re: [Seaside] flow<br>To: <a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a><br>
<br>Embed what? In the end you still have to return a response and you can either return an HTML response or a PDF response... you can't return both. If you return a PDF, there is no way for the user to proceed further down that branch of the control flow (unless you were generating a PDF with callback links inside it :) ). It is, effectively, a dead branch, so #answering after returning a PDF doesn't make sense to me.<br>
<br>I'm still struggling to understand the flow that Milan is envisioning...<br><br>Julian<br><br><div>On Thu, Jun 16, 2011 at 11:52 PM, Robert Sirois <span dir="ltr"><<a href="mailto:watchlala@hotmail.com" target="_blank">watchlala@hotmail.com</a>></span> wrote:<br>
<blockquote style="border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">Mayhaps embedding it? It would be easy enough for the user to download then.<br><br>RS<br><br><hr>From: <a href="mailto:jfitzell@gmail.com" target="_blank">jfitzell@gmail.com</a><br>Date: Thu, 16 Jun 2011 23:43:31 +0100<br>
Subject: Re: [Seaside] flow<div><br>To: <a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a><br><br></div><div><div></div><div>On Thu, Jun 16, 2011 at 4:50 PM, Milan Mimica <span dir="ltr"><<a href="mailto:milan.mimica@gmail.com" target="_blank">milan.mimica@gmail.com</a>></span> wrote:<br>
<div><blockquote style="border-left:1px #ccc solid;padding-left:1ex">
<div>Julian Fitzell wrote:<br>
<blockquote 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></div></div>_______________________________________________
seaside mailing list
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a> </div></div>
<br>_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
<br></blockquote></div><br>
<br>_______________________________________________
seaside mailing list
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a></div></div></div> </div></div>
<br>_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
<br></blockquote></div><br>