Re: [cgiapp] Re: RFC: CGI::Application::Plugin::Output::PDF

[Michael Peters <suppressed>]

Evan A. Zacks wrote:

> Thanks for the insight. I agree that it would be unusual to want
> pdf output for all runmodes. If that were desired, then the user
> might be better off using PDF::Template directly, for example.
> 
> Cees Hek had an interesting idea yesterday -- allow the user to
> specify a form parameter that controls whether or not to generate
> pdf output. In the configuration phase, the user can set a form
> field, say 'pdf_output', that will be examined in the postrun
> callback installed by this plugin. (A reasonable default will be
> supplied)
> 
> If that form field is set (by the browser), then pdf conversion
> will take place. Otherwise, the postrun callback won't do
> anything. This allows the programmer to use the plugin without
> needing to explicitly call the pdf output conversion method.
> 
> Another related suggestion was to allow the user to specify a
> list of runmodes where pdf output would be allowed (or
> disallowed). Does anyone have a preference for which would be
> better (or if we should have both)?

I like both of them :)
The first suggestion would allow you to easily create a pdf of the HTML
that you just sent to the user, but I can also see the need to have a
PDF of something that is never actually seen in HTML by the user.

-- 
Michael Peters
Developer
Plus Three, LP


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed