view release on metacpan or search on metacpan
lib/CAD/Drawing/IO/Image.pm view on Meta::CPAN
# $CAD::Drawing::default_color{$self} = $defaultcolor; # XXX ?
if($opts{bgcolor}) {
$bgcolor = $opts{bgcolor};
}
$outobj->ReadImage("xc:$bgcolor");
if($opts{transparent}) {
$outobj->Transparent(color=>"$bgcolor");
}
unless($opts{prescaled}) {
carp("must prescale drawing object for now\n");
# FIXME: this should now go into the fit-to-bound deal
view release on metacpan or search on metacpan
lib/CAM/UserApp.pm view on Meta::CPAN
passthru => string
An accumulation of CGI parameters passed to this program, in the form
of '<input type=hidden name=key value=value>' for each parameter.
Implementations are welcome to ignore this, but they should pass it
via an HTML form if they want to make the login be 'transparent',
i.e., if the program should go back to whatever it was doing before
when login is successful login.
Here's an example HTML template file for use with the offerLogin()
implementation in the Synopsis above, using these parameters:
view release on metacpan or search on metacpan
lib/CDB/TinyCDB/Wrapper.pm view on Meta::CPAN
use CDB::TinyCDB;
=head1 NAME
CDB::TinyCDB::Wrapper - A wrapper around CDB::TinyCDB to try and make
updating its files a little more transparent
=head1 VERSION
Version 0.03
view release on metacpan or search on metacpan
lib/CDDB.pm view on Meta::CPAN
}
}
#------------------------------------------------------------------------------
# Connect to a cddbp server. Connecting and disconnecting are done
# transparently and are performed on the basis of need. Furthermore,
# this routine will cycle through servers until one connects or it has
# exhausted all its possibilities. Returns true if successful, or
# false if failed.
sub connect {
view release on metacpan or search on metacpan
lib/CGI/Alert.pm view on Meta::CPAN
=head1 SYNOPSIS
use CGI::Alert 'youraddress@your.domain';
That's all. Everything else is transparent to your script.
Or:
use CGI::Alert qw(you@your.domain http_die);
...
view release on metacpan or search on metacpan
misc/style.css view on Meta::CPAN
color: #ff6600;
text-decoration: underline;
}
A:link, A:visited {
background: transparent;
color: #006699;
}
A[href="#POD_ERRORS"] {
background: transparent;
color: #FF0000;
}
TD {
margin: 0;
misc/style.css view on Meta::CPAN
padding: 0.4ex 1ex;
text-align: left;
}
TH A:link, TH A:visited {
background: transparent;
color: black;
}
.box {
border: 1px solid #006699;
misc/style.css view on Meta::CPAN
padding: 0.5ex 1ex;
vertical-align: baseline;
}
.path A {
background: transparent;
color: #006699;
font-weight: bold;
}
.pages {
misc/style.css view on Meta::CPAN
margin: 1ex 0;
padding: 1px;
}
.menubar .links {
background: transparent;
color: white;
padding: 0.2ex;
text-align: left;
}
misc/style.css view on Meta::CPAN
font: bold 10pt Arial,Helvetica,sans-serif;
text-decoration: none;
}
A.o:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
A.m:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
table.dlsip {
misc/style.css view on Meta::CPAN
padding: 1em;
white-space: pre;
}
.pod H1 {
background: transparent;
color: #006699;
font-size: large;
}
.pod H2 {
background: transparent;
color: #006699;
font-size: medium;
}
.pod IMG {
misc/style.css view on Meta::CPAN
.chmenu TD {
padding: 0.2ex 1ex;
}
.chmenu A:link, .chmenu A:visited {
background: transparent;
color: white;
text-decoration: none;
}
.chmenu A:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
.column {
misc/style.css view on Meta::CPAN
margin: auto;
width: 14em;
}
.date {
background: transparent;
color: #008000;
}
view release on metacpan or search on metacpan
lib/CGI/Application/PhotoGallery/GD.pm view on Meta::CPAN
return $self;
}
=head2 resize( $file, $size )
Resizes C<$file> to C<$size>xC<$size> with transparent margins.
=cut
sub resize {
my $self = shift;
lib/CGI/Application/PhotoGallery/GD.pm view on Meta::CPAN
my ( $width, $height ) = $image->getBounds();
my $image2 = new GD::Image( $size, $size );
$image2->transparent( $image2->colorAllocate( 0, 0, 0 ) );
my $hnw = int( ( $height * $size / $width ) + 0.5 );
my $wnh = int( ( $width * $size / $height ) + 0.5 );
my @arg = ( $image, 0, 0, 0, 0, $size, $size, $width, $height );
view release on metacpan or search on metacpan
misc/style.css view on Meta::CPAN
color: #ff6600;
text-decoration: underline;
}
A:link, A:visited {
background: transparent;
color: #006699;
}
A[href="#POD_ERRORS"] {
background: transparent;
color: #FF0000;
}
TD {
margin: 0;
misc/style.css view on Meta::CPAN
padding: 0.4ex 1ex;
text-align: left;
}
TH A:link, TH A:visited {
background: transparent;
color: black;
}
.box {
border: 1px solid #006699;
misc/style.css view on Meta::CPAN
padding: 0.5ex 1ex;
vertical-align: baseline;
}
.path A {
background: transparent;
color: #006699;
font-weight: bold;
}
.pages {
misc/style.css view on Meta::CPAN
margin: 1ex 0;
padding: 1px;
}
.menubar .links {
background: transparent;
color: white;
padding: 0.2ex;
text-align: left;
}
misc/style.css view on Meta::CPAN
font: bold 10pt Arial,Helvetica,sans-serif;
text-decoration: none;
}
A.o:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
A.m:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
table.dlsip {
misc/style.css view on Meta::CPAN
padding: 1em;
white-space: pre;
}
.pod H1 {
background: transparent;
color: #006699;
font-size: large;
}
.pod H2 {
background: transparent;
color: #006699;
font-size: medium;
}
.pod IMG {
misc/style.css view on Meta::CPAN
.chmenu TD {
padding: 0.2ex 1ex;
}
.chmenu A:link, .chmenu A:visited {
background: transparent;
color: white;
text-decoration: none;
}
.chmenu A:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
.column {
misc/style.css view on Meta::CPAN
margin: auto;
width: 14em;
}
.date {
background: transparent;
color: #008000;
}
view release on metacpan or search on metacpan
local/lib/perl5/Module/Build/Bundling.pod view on Meta::CPAN
module_name => 'Foo::Bar',
license => 'perl',
)->create_build_script;
A "bundling" Build.PL replaces the initial "use" line with a nearly
transparent replacement:
use inc::latest 'Module::Build';
Module::Build->new(
module_name => 'Foo::Bar',
view release on metacpan or search on metacpan
lib/CGI/Application/Plugin/CompressGzip.pm view on Meta::CPAN
=head1 DESCRIPTION
This plugin automatically enables gzip content encoding in your CGI::Application
program where appropriate. This reduces bandwidth, which is good for your server,
and for your site's responsiveness. You "use" it once in your base class, and
the rest is transparent.
It does its work by overriding cgiapp_get_query, which returns a new
CGI::Compress::Gzip object instead of the default CGI object.
=head1 EXPORTS
view release on metacpan or search on metacpan
misc/style.css view on Meta::CPAN
color: #ff6600;
text-decoration: underline;
}
A:link, A:visited {
background: transparent;
color: #006699;
}
A[href="#POD_ERRORS"] {
background: transparent;
color: #FF0000;
}
TD {
margin: 0;
misc/style.css view on Meta::CPAN
padding: 0.4ex 1ex;
text-align: left;
}
TH A:link, TH A:visited {
background: transparent;
color: black;
}
.box {
border: 1px solid #006699;
misc/style.css view on Meta::CPAN
padding: 0.5ex 1ex;
vertical-align: baseline;
}
.path A {
background: transparent;
color: #006699;
font-weight: bold;
}
.pages {
misc/style.css view on Meta::CPAN
margin: 1ex 0;
padding: 1px;
}
.menubar .links {
background: transparent;
color: white;
padding: 0.2ex;
text-align: left;
}
misc/style.css view on Meta::CPAN
font: bold 10pt Arial,Helvetica,sans-serif;
text-decoration: none;
}
A.o:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
A.m:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
table.dlsip {
misc/style.css view on Meta::CPAN
padding: 1em;
white-space: pre;
}
.pod H1 {
background: transparent;
color: #006699;
font-size: large;
}
.pod H2 {
background: transparent;
color: #006699;
font-size: medium;
}
.pod IMG {
misc/style.css view on Meta::CPAN
.chmenu TD {
padding: 0.2ex 1ex;
}
.chmenu A:link, .chmenu A:visited {
background: transparent;
color: white;
text-decoration: none;
}
.chmenu A:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
.column {
misc/style.css view on Meta::CPAN
margin: auto;
width: 14em;
}
.date {
background: transparent;
color: #008000;
}
view release on metacpan or search on metacpan
misc/style.css view on Meta::CPAN
color: #ff6600;
text-decoration: underline;
}
A:link, A:visited {
background: transparent;
color: #006699;
}
A[href="#POD_ERRORS"] {
background: transparent;
color: #FF0000;
}
TD {
margin: 0;
misc/style.css view on Meta::CPAN
padding: 0.4ex 1ex;
text-align: left;
}
TH A:link, TH A:visited {
background: transparent;
color: black;
}
.box {
border: 1px solid #006699;
misc/style.css view on Meta::CPAN
padding: 0.5ex 1ex;
vertical-align: baseline;
}
.path A {
background: transparent;
color: #006699;
font-weight: bold;
}
.pages {
misc/style.css view on Meta::CPAN
margin: 1ex 0;
padding: 1px;
}
.menubar .links {
background: transparent;
color: white;
padding: 0.2ex;
text-align: left;
}
misc/style.css view on Meta::CPAN
font: bold 10pt Arial,Helvetica,sans-serif;
text-decoration: none;
}
A.o:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
A.m:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
table.dlsip {
misc/style.css view on Meta::CPAN
padding: 1em;
white-space: pre;
}
.pod H1 {
background: transparent;
color: #006699;
font-size: large;
}
.pod H2 {
background: transparent;
color: #006699;
font-size: medium;
}
.pod IMG {
misc/style.css view on Meta::CPAN
.chmenu TD {
padding: 0.2ex 1ex;
}
.chmenu A:link, .chmenu A:visited {
background: transparent;
color: white;
text-decoration: none;
}
.chmenu A:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
.column {
misc/style.css view on Meta::CPAN
margin: auto;
width: 14em;
}
.date {
background: transparent;
color: #008000;
}
view release on metacpan or search on metacpan
lib/CGI/Application/Plugin/DBIProfile/Graph/GDGraphInline.pm view on Meta::CPAN
# build the graph image
my $graph_data;
{
our @BARS;
my $graph = GD::Graph::bars->new($WIDTH, $HEIGHT);
$graph->set(transparent => 0,
bgclr => '#FFFFFF',
legend_placement => 'BC',
x_ticks => 0,
cycle_clrs => 1,
bar_spacing => 5,
view release on metacpan or search on metacpan
misc/style.css view on Meta::CPAN
color: #ff6600;
text-decoration: underline;
}
A:link, A:visited {
background: transparent;
color: #006699;
}
A[href="#POD_ERRORS"] {
background: transparent;
color: #FF0000;
}
TD {
margin: 0;
misc/style.css view on Meta::CPAN
padding: 0.4ex 1ex;
text-align: left;
}
TH A:link, TH A:visited {
background: transparent;
color: black;
}
.box {
border: 1px solid #006699;
misc/style.css view on Meta::CPAN
padding: 0.5ex 1ex;
vertical-align: baseline;
}
.path A {
background: transparent;
color: #006699;
font-weight: bold;
}
.pages {
misc/style.css view on Meta::CPAN
margin: 1ex 0;
padding: 1px;
}
.menubar .links {
background: transparent;
color: white;
padding: 0.2ex;
text-align: left;
}
misc/style.css view on Meta::CPAN
font: bold 10pt Arial,Helvetica,sans-serif;
text-decoration: none;
}
A.o:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
A.m:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
table.dlsip {
misc/style.css view on Meta::CPAN
padding: 1em;
white-space: pre;
}
.pod H1 {
background: transparent;
color: #006699;
font-size: large;
}
.pod H2 {
background: transparent;
color: #006699;
font-size: medium;
}
.pod IMG {
misc/style.css view on Meta::CPAN
.chmenu TD {
padding: 0.2ex 1ex;
}
.chmenu A:link, .chmenu A:visited {
background: transparent;
color: white;
text-decoration: none;
}
.chmenu A:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
.column {
misc/style.css view on Meta::CPAN
margin: auto;
width: 14em;
}
.date {
background: transparent;
color: #008000;
}
view release on metacpan or search on metacpan
misc/style.css view on Meta::CPAN
color: #ff6600;
text-decoration: underline;
}
A:link, A:visited {
background: transparent;
color: #006699;
}
A[href="#POD_ERRORS"] {
background: transparent;
color: #FF0000;
}
TD {
margin: 0;
misc/style.css view on Meta::CPAN
padding: 0.4ex 1ex;
text-align: left;
}
TH A:link, TH A:visited {
background: transparent;
color: black;
}
.box {
border: 1px solid #006699;
misc/style.css view on Meta::CPAN
padding: 0.5ex 1ex;
vertical-align: baseline;
}
.path A {
background: transparent;
color: #006699;
font-weight: bold;
}
.pages {
misc/style.css view on Meta::CPAN
margin: 1ex 0;
padding: 1px;
}
.menubar .links {
background: transparent;
color: white;
padding: 0.2ex;
text-align: left;
}
misc/style.css view on Meta::CPAN
font: bold 10pt Arial,Helvetica,sans-serif;
text-decoration: none;
}
A.o:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
A.m:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
table.dlsip {
misc/style.css view on Meta::CPAN
padding: 1em;
white-space: pre;
}
.pod H1 {
background: transparent;
color: #006699;
font-size: large;
}
.pod H2 {
background: transparent;
color: #006699;
font-size: medium;
}
.pod IMG {
misc/style.css view on Meta::CPAN
.chmenu TD {
padding: 0.2ex 1ex;
}
.chmenu A:link, .chmenu A:visited {
background: transparent;
color: white;
text-decoration: none;
}
.chmenu A:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
.column {
misc/style.css view on Meta::CPAN
margin: auto;
width: 14em;
}
.date {
background: transparent;
color: #008000;
}
view release on metacpan or search on metacpan
misc/style.css view on Meta::CPAN
color: #ff6600;
text-decoration: underline;
}
A:link, A:visited {
background: transparent;
color: #006699;
}
A[href="#POD_ERRORS"] {
background: transparent;
color: #FF0000;
}
TD {
margin: 0;
misc/style.css view on Meta::CPAN
padding: 0.4ex 1ex;
text-align: left;
}
TH A:link, TH A:visited {
background: transparent;
color: black;
}
.box {
border: 1px solid #006699;
misc/style.css view on Meta::CPAN
padding: 0.5ex 1ex;
vertical-align: baseline;
}
.path A {
background: transparent;
color: #006699;
font-weight: bold;
}
.pages {
misc/style.css view on Meta::CPAN
margin: 1ex 0;
padding: 1px;
}
.menubar .links {
background: transparent;
color: white;
padding: 0.2ex;
text-align: left;
}
misc/style.css view on Meta::CPAN
font: bold 10pt Arial,Helvetica,sans-serif;
text-decoration: none;
}
A.o:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
A.m:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
table.dlsip {
misc/style.css view on Meta::CPAN
padding: 1em;
white-space: pre;
}
.pod H1 {
background: transparent;
color: #006699;
font-size: large;
}
.pod H2 {
background: transparent;
color: #006699;
font-size: medium;
}
.pod IMG {
misc/style.css view on Meta::CPAN
.chmenu TD {
padding: 0.2ex 1ex;
}
.chmenu A:link, .chmenu A:visited {
background: transparent;
color: white;
text-decoration: none;
}
.chmenu A:hover {
background: transparent;
color: #ff6600;
text-decoration: underline;
}
.column {
misc/style.css view on Meta::CPAN
margin: auto;
width: 14em;
}
.date {
background: transparent;
color: #008000;
}
view release on metacpan or search on metacpan
lib/Apache/Application/Magic.pm view on Meta::CPAN
=head2 Perl Side Include
SSI (Server Side Includes) are directives that are placed in HTML pages, and evaluated on the server while the pages are being served. The Apache server uses the C<mod_include> Apache module to process the pages, but you can configure it to process t...
In other words: your own C<Apache::Application::Magic> based module transparently process the pages of a web dir, supplying the dinamic content that will be included in the page just before they are served.
With this technique B<your application does not need to handle neither run modes, nor run methods, nor template managements>: all that is auto-magically handled by the C<Apache::Application::Magic> super class.
Please, take a look at the 'perl_side_include' example in this distribution to understand all the advantages offered by this technique.
view release on metacpan or search on metacpan
=pod
=item C<FormFields>
Returns HTML code for placing existing CGI parameters on a form so that the
login process is transparent to the calling script.
For any single-valued parameters, it creates a hidden C<< <input> >> control,
and for any multi-valued parameters, it creates a hidden (i.e.,
C<style="display: none">) C<< <select> >> control with all of its values.
view release on metacpan or search on metacpan
AuthRegister.pm view on Meta::CPAN
=head1 DESCRIPTION
CGI::AuthRegister is a Perl module for CGI user authentication and
registration. It is created with objective to be simple, flexible,
and transparent. For the sake of simplicity, it is not completely
portable, but mostly designed for Linux environment. As an example,
it relies on a directly calling sendmail for sending email messages.
Example 1, included in the distribution, and shown above, illustrates
the main functionalities of the module in one CGI file. The module is
AuthRegister.pm view on Meta::CPAN
=head1 SEE ALSO
There are already several modules for CGI authentication in Perl, but
they do not seem to satisfy some specific requirements, that could be
vaguely described as: simple, flexible, robust, and transparent.
Additionally, they do not typically include registration process for
new users and password reminders using email, which are added here.
These are some of the current implementation:
view release on metacpan or search on metacpan
lib/CGI/Builder/CgiAppAPI.pm view on Meta::CPAN
=head1 DESCRIPTION
B<Note>: You should know L<CGI::Builder>.
This module supplies an API compatible with the C<CGI::Application> or C<CGI::Application::Plus> APIs. It transparently provides all the aliases, defaults and method redefinition to make the old cgiapps work unchanged under CBF as well. Besides, it p...
B<WARNING>: This module is not intended to be used neither as an alternative API for the CBF nor in a production environment. You should use it only as:
=over
lib/CGI/Builder/CgiAppAPI.pm view on Meta::CPAN
The CBF let you organize your application in a far more flexible way, it just need to find some C<page_content> to send to the client: it does not matter what method or handler has set it during the process, (and the C<page_content> itself might even...
This flexible structure open several handy and powerful possibilities to your application and to the extension system. If you want to know some more details about that, you could read L<CGI::Application::Plus/"Exclusive Features and Improvements"> wh...
B<Note>: The changes reported below are needed just if you want to completely convert your old cgiapp to the CBF. Until you include this API in your build, they are transparently added to your application.
=head2 mode_param
Change it with C<cgi_page_param>.
view release on metacpan or search on metacpan
lib/CGI/Builder/HTMLtmpl.pm view on Meta::CPAN
=head1 DESCRIPTION
B<Note>: You should know L<CGI::Builder>.
This module transparently integrates C<CGI::Builder> and C<HTML::Template> in a very handy and flexible framework that can save you some coding. It provides you a mostly automatic template system based on HTML::Template: usually you will have just to...
B<Note>: With this extension you don't need to explicitly set the C<page_content> to the output of your template object (C<< ht->output() >>) in your Page Handlers, because it will be automatically set. You should explicitly set the C<page_content> p...
# in order to produce the output with the template 'myPage.tmpl',
# usually you just need to pass the param to the object
view release on metacpan or search on metacpan
lib/CGI/Builder/Magic.pm view on Meta::CPAN
=head1 DESCRIPTION
B<Note>: You should know L<CGI::Builder>.
This module transparently integrates C<CGI::Builder> and C<Template::Magic> in a very handy, powerful and flexible framework that can save you a lot of coding, time and resources.
With this module, you don't need to produce the C<page_content> within your page handlers anymore (unless you want to); you don't even need to manage a template system yourself (unless you want to).
If you use any template system on your own (i.e. not integrated in a CBF extension), you will have to write all this code explicitly:
lib/CGI/Builder/Magic.pm view on Meta::CPAN
run the template process and set the C<page_content> to the produced output
=back
You can save all that by just including this module in your build, because it implements an internal transparent and automagic template system that even without your explicit intervention is capable of finding the correct template and the correct run...
=head2 How to organize your CBB
Add these steps to the recommendations in L<CGI::Builder/"Design your application">:
lib/CGI/Builder/Magic.pm view on Meta::CPAN
=head2 Apache::CGI::Builder (Perl Side Include)
SSI (Server Side Includes) are directives that are placed in HTML pages, and evaluated on the server while the pages are being served. The Apache server uses the C<mod_include> Apache module to process the pages, but you can configure it to process t...
In other words: your own CBB transparently process the pages of a web dir, supplying the dinamic content that will be included in the page just before they are served.
With this technique B<your application does not need to handle neither page names, nor page handlers, nor template managements>: all that is auto-magically handled by the combination of C<Apache::CGI::Builder> and C<CGI::Builder::Magic> extensions.
Please, take a look at the 'perl_side_include' example in this distribution to understand all the advantages offered by this technique.
view release on metacpan or search on metacpan
lib/CGI/Builder/Session.pm view on Meta::CPAN
=head1 DESCRIPTION
B<Note>: You should know L<CGI::Builder>.
This module transparently integrates C<CGI::Builder> and C<CGI::Session> in a very handy and flexible framework that can save you some coding. It provides you a mostly automatic and ready to use CGI::Session object (C<cs> property) useful to maintain...
=head2 How it works
This extension creates a CGI::Session object automatically, using the old session id if it is found as a cookie or as a query param. If no session id is found, it creates a new session and automatically adds a session id cookie and a session id param...
view release on metacpan or search on metacpan
lib/CGI/Builder/TT2.pm view on Meta::CPAN
qw| CGI::Builder::TT2
|;
=head1 DESCRIPTION
This module transparently integrates C<CGI::Builder> and C<Template> in
a very handy, powerful and flexible framework that can save you a lot of
coding, time and resources.
With this module, you don't need to produce the C<page_content> within
your page handlers anymore (unless you want to); you don't even need to
lib/CGI/Builder/TT2.pm view on Meta::CPAN
output
=back
You can save all that by just including this module in your build,
because it implements an internal transparent and automatic template
system that even without your explicit intervention is capable of
finding the correct template and the correct runtime values to fill it,
and generates the page_content automagically. With this module you can
even eliminate the page handlers that are just setting the page_content,
because the page is automatically sent by the template system.
view release on metacpan or search on metacpan
lib/CGI/Builder.pm view on Meta::CPAN
#!/usr/bin/perl -w
use My::WebApp ;
$webapp = My::WebApp->new() ;
$webapp->process() ;
B<Note>: This script could be completely eliminated by the use of the C<Apache::CGI::Builder> extension (usable under mod_perl) which transparently executes the process.
=head2 CGI Builder Build (CBB)
This is the part of your application that implements the CBF features.
view release on metacpan or search on metacpan
1.01 Mon Oct 2 18:18:25 EDT 2000
- Maintenance handed over to David Coppit <david@coppit.org>. All
changes in this version are made by him.
- Underlying caching is now handled by File::Cache. This allows for extra
features such as cache maximum sizes, transparent cache entry expiration,
etc.
- The cache key can now be any data structure instead of just a simple
string. This means that one can just hand the CGI parameters directly to
CGI::Cache and it will figure out a suitable stringified cache key.
- Because File::Cache now does most of the cache management automatically,
view release on metacpan or search on metacpan
lib/CGI/Compress/Gzip.pm view on Meta::CPAN
chooses HTML output, apply gzip compression on any content header for
STDOUT. This module is intended to be a drop-in replacement for
CGI.pm.
Apache mod_perl users may wish to consider the Apache::Compress or
Apache::GzipChain modules, which allow more transparent output
compression than this module can provide. However, as of this writing
those modules are more aggressive about compressing, regardless of
Content-Type.
=head2 Headers
view release on metacpan or search on metacpan
lib/CGI/FormBuilder.pm view on Meta::CPAN
# and storing them into a temp hash, and then going thru
# the fields and picking up the values and attributes.
local $" = ',';
debug 1, "\$form->{values} = ($self->{values})";
# Using isa() allows objects to transparently fit in here
if (UNIVERSAL::isa($self->{values}, 'CODE')) {
# it's a sub; lookup each value in turn
for my $key (&{$self->{values}}) {
# always assume an arrayref of values...
$val{$key} = [ &{$self->{values}}($key) ];
view release on metacpan or search on metacpan
scripts/generate_index.pl view on Meta::CPAN
margin-bottom: 4px;
}
/* Ensure the test code block inherits readable colors */
.suggested-test pre {
background: transparent; /* Prevent nested dark blocks */
color: inherit; /* Match theme text color */
margin: 0;
font-family: monospace;
}
view release on metacpan or search on metacpan
The Fh package still exists but does nothing, the CGI::File::Temp class is
a subclass of both File::Temp and the empty Fh package, so if you have any
code that checks that the filehandle isa Fh this should still work.
When you get the internal file handle you will receive a File::Temp object,
this should be transparent as File::Temp isa IO::Handle and isa IO::Seekable
meaning it behaves as previously. If you are doing anything out of the ordinary
with regards to temp files you should test your code before deploying this
update and refer to the File::Temp documentation for more information.
### Handling interrupted file uploads