On 2005-09-23, Evan A. Zacks <[EMAIL PROTECTED]> wrote:
>
> 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.
I can see this a useful option when you want an easy to offer users the
ability to print the run mode as a PDF.
A more direct an explicit way to generate PDFs should still be provided.
> 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)?
If this would be like "run_modes()" in setup, I don't like the idea,
because it's far enough way from where the action is to cause confusion.
I would rather see a subroutine attribute be used:
sub display_list : Runmode, AllowPDF {
# ....
}
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
[EMAIL PROTECTED] Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
