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
lib/CGI/Inspect/htdocs/js/jquery.ui.all.js view on Meta::CPAN
* Copyright (c) 2009 AUTHORS.txt (http://jqueryui.com/about)
* Dual licensed under the MIT (MIT-LICENSE.txt)
* and GPL (GPL-LICENSE.txt) licenses.
*
* http://docs.jquery.com/UI/Effects/
*/
jQuery.effects||(function(d){d.effects={version:"1.7.1",save:function(g,h){for(var f=0;f<h.length;f++){if(h[f]!==null){g.data("ec.storage."+h[f],g[0].style[h[f]])}}},restore:function(g,h){for(var f=0;f<h.length;f++){if(h[f]!==null){g.css(h[f],g.d...
* jQuery UI Effects Blind 1.7.1
*
* Copyright (c) 2009 AUTHORS.txt (http://jqueryui.com/about)
* Dual licensed under the MIT (MIT-LICENSE.txt)
* and GPL (GPL-LICENSE.txt) licenses.
view release on metacpan or search on metacpan
lib/CGI/Lazy.pm view on Meta::CPAN
Lazy has also been written to be useful in a mod_perl environment if that is your pleasure. The wonders of persistence and namespaces have been (again, hopefully) all accounted for. It should plug into your mod_perl environment with little or no fu...
For the most part, CGI::Lazy is simply a subclass of CGI::Pretty, which is an easier to read version of CGI.pm.
We need to use CGI::Pretty due to a css issue in IE where the style definitions aren't always followed unless there is the appropriate amount of whitespace between html tags. Luckilly, CGI::Pretty takes care of this pretty transparently, and its out...
CGI::Lazy adds a bunch of hooks in the interest of not working any harder than we need to, otherwise it's a CGI::Pretty object.
Probably 80% of the apps the author has been asked to write have been front ends to some sort of database, so that's definitely the angle Lazy is coming from. It works just fine with no db, but most of the fancy work is unavailable.
Output to the web is intended to be through templates via HTML::Template. However, if you want to write your content into the code manually, we won't stop you. Again, the whole point was to be flexible and reusable, and to spend our time writing ne...
The CGI::Lazy::Widget::Dataset module especially was written to bring spreadsheet-like access to a database table to the web in a fairly transparent manner- after all, most of the time you're doing one of 4 operations on a database: select, insert, u...
In any event, it is my hope that this is useful to you. It has saved me quite alot of work. I hope that it can do the same for you. Bug reports and comments are always welcome.
=head1 METHODS
view release on metacpan or search on metacpan
MxScreen/Serializer/Storable.pm view on Meta::CPAN
Whether to compress the serialized form before returning it.
Data will be uncompressed on-the-fly by the C<deserialize> routine.
It is I<false> by default.
This makes compression transparent once configured.
=item C<-shared> => I<flag>
Whether serialized data are expected to be shared across different
architectures. When I<true>, C<Storable> will use its portable format
view release on metacpan or search on metacpan
lib/CGI/OptimalQuery/InteractiveQuery.pm view on Meta::CPAN
.OQaddColButton, .OQsortAscButton, .OQsortDescButton, .OQfilterCol, .OQcloseButton{
width: 15px; height: 16px; margin: 0; margin-right: 8px !important; padding: 0;
border: 0 !important; text-indent: -1000em;
}
.OQaddColButton { background: transparent url(/OptimalQuery/add.gif) no-repeat center top; }
.OQsortAscButton { background: transparent url(/OptimalQuery/sortDown.gif) no-repeat center top; }
.OQsortDescButton { background: transparent url(/OptimalQuery/sortUp.gif) no-repeat center top; }
.OQfilterCol { background: transparent url(/OptimalQuery/filter.gif) no-repeat center top; }
.OQcloseButton { background: transparent url(/OptimalQuery/close.gif) no-repeat center top; }
#cmdOptions {
margin-top: 10px;
position: absolute;
width: 20em;
view release on metacpan or search on metacpan
lib/CGI/Persistent.pm view on Meta::CPAN
CGI::Persistent solves this problem by introducing persistent CGI sessions
that store their state data on the server side. When a new session starts,
CGI::Persistent automatically generates a unique state identification string
and associates it with a persistent object on the server. The identification
string is used in URLs or forms to refer to the particular session. Request
attributes are transparently committed to the associated object and the
object data is bound to the query.
CGI::Persistent is derived from CGI.pm. CGI.pm methods have been overridden
as appropriate. Very few new methods have been added.
view release on metacpan or search on metacpan
demos/image/DemoDrawImage.pm view on Meta::CPAN
my $white = $im->colorAllocate(255,255,255);
my $black = $im->colorAllocate(0,0,0);
my $red = $im->colorAllocate(255,0,0);
my $blue = $im->colorAllocate(0,0,255);
# make the background transparent and interlaced
$im->transparent($white);
$im->interlaced('true');
# Put a black frame around the picture
$im->rectangle(0,0,99,99,$black);
view release on metacpan or search on metacpan
lib/CGI/PrintWrapper.pm view on Meta::CPAN
above). As the caller invokes B<CGI> methods, C<AUTOLOAD> creates
anonymous subroutines to perform the actual B<CGI> method call
indirection and print the results with the print handle object. It
also updates the symbol table for B<CGI::PrintWrapper> so that future
calls can bypass C<AUTOLOAD>. This makes a B<CGI::PrintWrapper>
object transparently a B<CGI> object, usable as a drop-in replacement.
=back
=head1 SEE ALSO
view release on metacpan or search on metacpan
lib/CGI/ProgressBar.pm view on Meta::CPAN
.pblib_block_on { border:1px solid blue; background: navy; }
";
if ($self->{progress_bar}->{label}){
$CSS .=".pblib_number {
text-align: right;
border: 1px solid transparent;
}";
}
$self->{progress_bar}->{css} = $CSS;
}
view release on metacpan or search on metacpan
lib/CGI/Screen.pm view on Meta::CPAN
my $h = GD::Font->$font()->height;
my $im = GD::Image->new((length($query->param('foo'))+2)*$w,$h);
my $white = $im->colorAllocate(255,255,255);
my $red = $im->colorAllocate(255,0,0);
my $black = $im->colorAllocate(0,0,0);
$im->transparent($white);
$im->arc(8,8,5,5,0,360,$red);
$im->string(GD::Font->$font(),10,0,$query->param('foo'),$black);
print $im->gif;
}
view release on metacpan or search on metacpan
realize that all your scripts have nasty warnings at the top. Perhaps yours
are more relaxed than that, but now that I have your attention, read the
documentation anyway as it contains important updates.
CGI::SecureState is a module that provides a transparent and secure way to
maintain state between HTTP requests. It was originally written to resemble
CGI::Persistent as closely as possible. To install CGI::SecureState, all you
should have to do is the standard
% perl Makefile.PL
view release on metacpan or search on metacpan
lib/CGI/Session/Tutorial.pm view on Meta::CPAN
User will not have sensitive data stored in his/her computer in unsecured file (which is a cookie file).
=item *
It's possible to handle very big and even complex data structures transparently (which I<HTTP Cookies> do not handle).
=back
That's what CGI::Session is all about - implementing server side session management. Now is a good time to get feet wet.
=head1 PROGRAMMING STYLE
Server side session management system might be seeming awfully convoluted if you have never dealt with it. Fortunately, with L<CGI::Session|CGI::Session> all the complexity is handled by the library transparently. This section of the manual can be tr...
All applications making use of server side session management rely on the following pattern of operation regardless of the way the system is implemented:
=over 4
view release on metacpan or search on metacpan
lib/CGI/Uploader/Transform/ImageMagick.pm view on Meta::CPAN
$orig_filename = $p{filename};
}
# we have the old ugly style API
else {
($orig_filename, $params) = validate_pos(@_,1,{ type => ARRAYREF });
# validate handles a hash or hashref transparently
%p = validate(@$params,{
w => { type => SCALAR | UNDEF, regex => qr/^\d*$/, optional => 1, },
h => { type => SCALAR | UNDEF, regex => qr/^\d*$/, optional => 1 },
});
}