<br><br><div class="gmail_quote">On Wed, May 6, 2009 at 5:28 PM, Andrew Rodland <span dir="ltr"><<a href="mailto:arodland@comcast.net">arodland@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">
<br>
</div>In that example you don't *have* a View::TTprint. Or if you do, it's just<br>
another subclas of C::V::TT with a different config and search path. No<br>
overloading, no OUTPUT. You forward to the view, it writes into $c->res->body<br>
like it always does. You take the data out of $c->res->body and write it to a<br>
file, then null out $c->res->body so that RenderView will fill it in later<br>
using your default_view.<br>
<font color="#888888"><br>
Andrew</font><br></blockquote></div><br>Thanks, Andrew, your explanation does help a great deal. The template output gets written out nicely, now. I feel I do want to use a separate view, because the files I'm writing out need to have their own templates, images, etc., so different search paths will help keep things neatly separated.<br>
<br>/dennis<br><br>