view release on metacpan or search on metacpan
share/cpan.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;
share/cpan.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;
share/cpan.css view on Meta::CPAN
padding: 0.5ex 1ex;
vertical-align: baseline;
}
.path A {
background: transparent;
color: #006699;
font-weight: bold;
}
.pages {
share/cpan.css view on Meta::CPAN
margin: 1ex 0;
padding: 1px;
}
.menubar .links {
background: transparent;
color: white;
padding: 0.2ex;
text-align: left;
}
share/cpan.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 {
share/cpan.css view on Meta::CPAN
padding: 1em;
white-space: pre;
}
.pod H1 {
background: transparent;
color: #006699;
font-size: large;
}
.pod H1 A { text-decoration: none; }
.pod H2 A { text-decoration: none; }
.pod H3 A { text-decoration: none; }
.pod H4 A { text-decoration: none; }
.pod H2 {
background: transparent;
color: #006699;
font-size: medium;
}
.pod H3 {
background: transparent;
color: #006699;
font-size: medium;
font-style: italic;
}
.pod H4 {
background: transparent;
color: #006699;
font-size: medium;
font-weight: normal;
}
share/cpan.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 {
share/cpan.css view on Meta::CPAN
margin: auto;
width: 14em;
}
.date {
background: transparent;
color: #008000;
}
.footer {
margin-top: 1ex;
view release on metacpan or search on metacpan
lib/Catalyst/Engine/HTTP/Prefork.pm view on Meta::CPAN
This engine fully supports the following HTTP/1.1 features:
=head2 Chunked Requests
Chunked body data is handled transparently by L<HTTP::Body>.
=head2 Chunked Responses
By setting the Transfer-Encoding header to 'chunked', you can indicate you
would like the response to be sent to the client as a chunked response. Also,
view release on metacpan or search on metacpan
lib/Catalyst/Manual/Components.pod view on Meta::CPAN
Lets you create a very quick and dirty user database in your application's
config hash. Great for testing or getting up and running quickly.
=head4 L<Catalyst::Authentication::Store::Null>
The Null store is a transparent store where any supplied user data is
accepted. This is mainly useful for remotely authenticating credentials
(e.g. OpenID) which may not be tied to any local storage.
=head4 L<Catalyst::Authentication::Store::RDBO>
view release on metacpan or search on metacpan
lib/Catalyst/Plugin/AtomServer.pm view on Meta::CPAN
=item * REST and SOAP interfaces
The Atom API supports either a REST interface or a SOAP interface using
a document-literal SOAP envelope. I<Catalyst::Plugin::AtomServer> supports
both interfaces, transparently for your application.
=item * Error Handling
I<Catalyst::Plugin::AtomServer> will automatically catch any exceptions
thrown by your application, and it will wrap the exception in the proper
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Store/Null.pm view on Meta::CPAN
}
});
=head1 DESCRIPTION
The Null store is a transparent store where any supplied user data is
accepted. This is mainly useful for remotely authenticating credentials
(e.g. TypeKey, OpenID) which may not be tied to any local storage. It also
helps facilitate integration with the Session plugin.
=head1 METHODS
view release on metacpan or search on metacpan
t/root/static/css/blueprint/print.css view on Meta::CPAN
blockquote {margin:1.5em;padding:1em;font-style:italic;font-size:.9em;}
.small {font-size:.9em;}
.large {font-size:1.1em;}
.quiet {color:#999;}
.hide {display:none;}
a:link, a:visited {background:transparent;font-weight:700;text-decoration:underline;}
a:link:after, a:visited:after {content:" (" attr(href) ")";font-size:90%;}
view release on metacpan or search on metacpan
lib/Catalyst/Plugin/HashedCookies.pm view on Meta::CPAN
=head2 Implementation
HashedCookies adds a keyed cryptographic hash to each cookie that your
application creates, and checks every client-provided cookie for a valid hash.
This is done in a transparent way such that you do not need to change B<any>
application code that handles cookies when using this plugin. A cookie that
fails to contain a valid hash will still be available to your application
through C<< $c->request->cookie() >>.
Two additional methods within the Catalyst request object allow you to check
view release on metacpan or search on metacpan
lib/Catalyst/Plugin/I18N/Request.pm view on Meta::CPAN
Localization involves taking paths and parameter names and replacing
them with values which make more sense to users speaking the requested
language. In the above example, 'search' may not look intuitive to
German users. Out of the box, this plugin allows you to localize these
values transparently via the standard $c->uri_for and
$c->request->uri_with methods which are already standard features of
the Catalyst framework.
Like delocalization, this functionality depends upon the $c->localize
method. However, PATH_delocalize_ is replaced with PATH_localize and
view release on metacpan or search on metacpan
lib/Catalyst/Plugin/Server/JSONRPC.pm view on Meta::CPAN
=item * Single entrypoint for JSONRPC calls, like http://host.tld/rpc
=item * DispatchTypes (attributes) which work much the same as Catalyst attrs
=item * JSONRPC Parameter handling transparent to Catalyst parameter handling
=back
=head1 HOW IT WORKS
lib/Catalyst/Plugin/Server/JSONRPC.pm view on Meta::CPAN
=back
=head1 CATALYST REQUEST
To make things transparent, we try to put JSONRPC params into the Request
object of Catalyst. But first we will explain something about the JSONRPC
specifications.
A full draft of these specifications can be found on:
C<http://www.jsonrpc.com/spec>
lib/Catalyst/Plugin/Server/JSONRPC.pm view on Meta::CPAN
}
=item $c->req->parameters
Because JSONRPC parameters are a LIST, we can't B<just> fill
$c->req->paremeters. To keep things transparent, we made an extra config
option what tells the JSONRPC server we can assume the following conditions
on all JSONRPC requests:
- There is only one JSONRPC parameter
- This JSONRPC parameter is a struct (HASH)
lib/Catalyst/Plugin/Server/JSONRPC.pm view on Meta::CPAN
=item Make stash filterable before returning
Just like the error messages, it would be nice to be able to filter the
stash before returning so you can filter out keys you don't want to
return to the client, or just return a certain list of keys.
This all to make transparent use of JSONRPC and web easier.
=back
=head1 SEE ALSO
view release on metacpan or search on metacpan
lib/Catalyst/Plugin/Server/XMLRPC.pm view on Meta::CPAN
=item * Single entrypoint for XMLRPC calls, like http://host.tld/rpc
=item * DispatchTypes (attributes) which work much the same as Catalyst attrs
=item * XMLRPC Parameter handling transparent to Catalyst parameter handling
=back
=head1 HOW IT WORKS
lib/Catalyst/Plugin/Server/XMLRPC.pm view on Meta::CPAN
=back
=head1 CATALYST REQUEST
To make things transparent, we try to put XMLRPC params into the Request
object of Catalyst. But first we will explain something about the XMLRPC
specifications.
A full draft of these specifications can be found on:
C<http://www.xmlrpc.com/spec>
lib/Catalyst/Plugin/Server/XMLRPC.pm view on Meta::CPAN
}
=item $c->req->parameters
Because XMLRPC parameters are a LIST, we can't B<just> fill
$c->req->paremeters. To keep things transparent, we made an extra config
option what tells the XMLRPC server we can assume the following conditions
on all XMLRPC requests:
- There is only one XMLRPC parameter
- This XMLRPC parameter is a struct (HASH)
lib/Catalyst/Plugin/Server/XMLRPC.pm view on Meta::CPAN
=item Make stash filterable before returning
Just like the error messages, it would be nice to be able to filter the
stash before returning so you can filter out keys you don't want to
return to the client, or just return a certain list of keys.
This all to make transparent use of XMLRPC and web easier.
=back
=head1 SEE ALSO
view release on metacpan or search on metacpan
lib/Catalyst/Plugin/Session/Tutorial.pod view on Meta::CPAN
</table>
As you can see the way that items are added into C<< $c->session->{cart} >> is
pretty simple. Since C<< $c->session >> is restored as necessary, and contains
data from previous requests by the same client, the cart can be updated as the
user navigates the site pretty transparently.
=head1 SECURITY ISSUES
These issues all relate to how session data is managed, as described above.
These are not issues you should be concerned about in your application code,
view release on metacpan or search on metacpan
0.21 2009-03-29 20:31:49
- Documentation improvements (jester)
- Change from NEXT to MRO::Compat - RT#40628, RT#44553 (ilmari)
- Bump prereq to MIME::Types to 1.25 to correctly send files
commonly used to graft support for transparent PNGs into
MSIE6 - RT#41314 (Florian Ragwitz)
0.20 2007-09-24 10:00:00
- Fixed issue where the static dir regex did not add a trailing
slash so URLs such as /static1 were served as static when they
view release on metacpan or search on metacpan
0.21 2009-03-29 20:31:49
- Documentation improvements (jester)
- Change from NEXT to MRO::Compat - RT#40628, RT#44553 (ilmari)
- Bump prereq to MIME::Types to 1.25 to correctly send files
commonly used to graft support for transparent PNGs into
MSIE6 - RT#41314 (Florian Ragwitz)
0.20 2007-09-24 10:00:00
- Fixed issue where the static dir regex did not add a trailing
slash so URLs such as /static1 were served as static when they
view release on metacpan or search on metacpan
lib/Catalyst/Plugin/UploadProgress.pm view on Meta::CPAN
$upload->copy_to( '/some/path/' . $upload->filename );
}
=head1 DESCRIPTION
This plugin is a simple, transparent method for displaying a
progress bar during file uploads.
=head1 DEMO
Please see the example/Upload directory in the distribution for a working
view release on metacpan or search on metacpan
lib/Catalyst/TraitFor/Request/REST/ForBrowsers/AndPJAX.pm view on Meta::CPAN
PJAX request is also a browser request, and thus looks_like_browser() also
returns true when the method is GET and the C<X-Pjax> header is present and is
'true'.
This allows actions using an action class of REST::ForBrowsers to
transparently handle PJAX requests, without requiring any more modification to
the controller or application than applying this trait to the request class,
rather than plain-old L<Catalyst::TraitFor::Request::REST::ForBrowsers>.
=head1 METHODS
view release on metacpan or search on metacpan
lib/Catalyst/Helper/View/Chart/Strip.pm view on Meta::CPAN
__PACKAGE__->config(
height => 192,
width => 720,
limit_factor => 1,
transparent => 0,
);
=head1 NAME
[% class %] - Catalyst Chart::Strip View
view release on metacpan or search on metacpan
examples/TestApp/root/static/css/superfish-navbar.css view on Meta::CPAN
background-position: -10px -100px; /* arrow hovers for modern browsers*/
}
/*** remove shadow on first submenu ***/
.sf-navbar > li > ul {
background: transparent;
padding: 0;
-moz-border-radius-bottomleft: 0;
-moz-border-radius-topright: 0;
-webkit-border-top-right-radius: 0;
-webkit-border-bottom-left-radius: 0;
view release on metacpan or search on metacpan
lib/Catalyst/View/Image/Text2Image.pm view on Meta::CPAN
$c->stash->{Text2Image}->{fgcolor} = 'green';
$c->stash->{Text2Image}->{moveTo} = [0,44];
$c->stash->{Text2Image}->{angle} = -5;
$c->stash->{Text2Image}->{morph} = 1; ### Should the x value be adapted when text is too long?
$c->stash->{Text2Image}->{clear} = 1; ### define "clear" to make canvas-color = bgcolor !!
$c->stash->{Text2Image}->{transparent} = 'white'; # set color to become transparent
$c->detach('View::Image::Text2Image');
}
=item Example to process a pre-created image with GD::Simple:
lib/Catalyst/View/Image/Text2Image.pm view on Meta::CPAN
Mandatory if not $c->stash->{Text2Image}->{img}
=item MORE Options...
More GD::Simple Options are just applied by values in the stash.
Tested in this version are: bgcolor, fgcolor, moveTo, clear, transparent and angle.
Refer to examples for more informations on that.
=back
=head2 Image format
lib/Catalyst/View/Image/Text2Image.pm view on Meta::CPAN
fontsize => 18,
string => 'Huhu..its me..your pic!',
### OPTIONAL Values:
morph => 1, # optional, will adapt x to string-width
clear => '1', # to set canvas-color=bgcolor.
transparent => 'white' # make background transparent
### other optional, GD::Simple Values:
fgcolor => 'black',
bgcolor => 'white',
angle => -5,
moveTo => [0,20] # Move pencil
view release on metacpan or search on metacpan
lib/Catalyst/View/JSON.pm view on Meta::CPAN
section provides some notes on various libraries.
Dojo Toolkit: Setting dojo.io.bind's mimetype to 'text/json' in
the JavaScript request will instruct dojo.io.bind to expect JSON
data in the response body and auto-eval it. Dojo ignores the
server response Content-Type. This works transparently with
Catalyst::View::JSON.
Prototype.js: prototype.js will auto-eval JSON data that is
returned in the custom X-JSON header. The reason given for this is
to allow a separate HTML fragment in the response body, however
view release on metacpan or search on metacpan
lib/CatalystX/CRUD/YUI/TT/static/css/crud/base.css view on Meta::CPAN
/* cursor:pointer; */
}
#crud-links li a.selected {
color: #222;
background: transparent url(http://yui.yahooapis.com/2.6.0/build/assets/skins/sam/menuitem_submenuindicator.png) no-repeat scroll right center;
background-color: #fff;
font-weight:bold;
cursor: default;
}
view release on metacpan or search on metacpan
lib/CatalystX/Crudite/Util/Random.pm view on Meta::CPAN
nonterminal
nonterminals
nonterminating
nontermination
nonthermal
nontransparent
nontrivial
nonuniform
nonuniformity
nonzero
noodle
lib/CatalystX/Crudite/Util/Random.pm view on Meta::CPAN
transmogrification
transmogrify
transpacific
transparencies
transparency
transparent
transparently
transpire
transpired
transpires
transpiring
transplant
view release on metacpan or search on metacpan
root/static/js/yui/build/animation/animation-min.js view on Meta::CPAN
Copyright (c) 2008, Yahoo! Inc. All rights reserved.
Code licensed under the BSD License:
http://developer.yahoo.net/yui/license.txt
version: 2.5.0
*/
(function(){var B=YAHOO.util;var A=function(D,C,E,F){if(!D){}this.init(D,C,E,F);};A.NAME="Anim";A.prototype={toString:function(){var C=this.getEl()||{};var D=C.id||C.tagName;return(this.constructor.NAME+": "+D);},patterns:{noNegatives:/width|height|o...
if(this.patterns.transparent.test(H)){var F=G.parentNode;H=C.Dom.getStyle(F,E);while(F&&this.patterns.transparent.test(H)){F=F.parentNode;H=C.Dom.getStyle(F,E);if(F.tagName.toUpperCase()=="HTML"){H="#fff";}}}}else{H=D.getAttribute.call(this,E);}retur...
/*
TERMS OF USE - EASING EQUATIONS
Open source under the BSD License.
Copyright 2001 Robert Penner All rights reserved.
view release on metacpan or search on metacpan
t/static/css/lists.css view on Meta::CPAN
}
.rowh {
background-color: #DDDDDD;
}
.rown {
/*background-color: transparent*/;
}
.select {
background-color: #d6dceb;
color: #333399;
font-size: 80%;
t/static/css/lists.css view on Meta::CPAN
input.textfield {
width: 100px;
}
select.select {
background-color: transparent;
font-weight: normal;
color: black;
font-family: Arial, Helvetica, sans-serif;
}
view release on metacpan or search on metacpan
misc/vim/syntax/catmandu-fix.vim view on Meta::CPAN
syntax keyword fixKeyword if else elsif unless bind do doset end and or
syntax keyword fixKeyword and or && ||
syntax match fix /[a-z][_0-9a-zA-Z]*\s*(/me=e-1,he=e-1
syntax region fixDoubleQuotedString start=/\v"/ skip=/\v\\./ end=/\v"/
syntax region fixSingleQuotedString start=/\v'/ skip=/\v\\./ end=/\v'/
syntax region fixIfBlock start="if" end="end" fold transparent
highlight default link fixComment Comment
highlight default link fixKeyword Keyword
highlight default link fix Function
highlight link fixDoubleQuotedString String
view release on metacpan or search on metacpan
lib/CfgTie/TieUser.pm view on Meta::CPAN
C<$CfgTie::TieUser_rec'userdel> contains the path to the program F<userdel>.
This can be modified as required.
Not all keys are supported on all systems.
This may transparently use a shadow tie in the future.
=head2 When the changes are reflected to /etc/passwd
=head1 Files
view release on metacpan or search on metacpan
lib/Chart/GGPlot/Backend/Plotly.pm view on Meta::CPAN
my $el_panel_border = $theme->at('panel_border');
unless ( not defined $el_panel_border or $el_panel_border->is_blank ) {
$plotly_layout{shapes} = [
{
type => 'rect',
fillcolor => 'transparent',
line => {
color => to_rgb( $el_panel_border->at('color') ),
width => 1,
linetype => 'solid',
},
view release on metacpan or search on metacpan
lib/Chart/Gnuplot/Util.pm view on Meta::CPAN
if (ref($fill) eq 'HASH')
{
my $style = "";
if (defined $$fill{pattern})
{
$style .= " transparent" if (defined $$fill{alpha} &&
$$fill{alpha} == 0);
$style .= " pattern $$fill{pattern}";
}
else
{
if (defined $$fill{alpha})
{
$style .= " transparent solid $$fill{alpha}";
}
elsif (defined $$fill{density})
{
$style .= " solid $$fill{density}";
}
view release on metacpan or search on metacpan
lib/Chart/OFC.pm view on Meta::CPAN
module's docs for more details.
=head2 Opacity
Several classes accept an opacity value for an attribute. This should
be a value from 0 (completely transparent) to 100 (completely opaque).
=head1 ATTRIBUTES
This class has a number of attributes which may be passed to the
C<new()> method.
view release on metacpan or search on metacpan
$self->{'_black'} = $self->{'_im'}->colorAllocate(0,0,0);
$self->{'_red'} = $self->{'_im'}->colorAllocate(255,0,0);
$self->{'_blue'} = $self->{'_im'}->colorAllocate(0,0,255);
$self->{'_green'} = $self->{'_im'}->colorAllocate(0,255,0);
# make the background transparent and interlaced
$self->{'_im'}->transparent($self->{'_white'});
$self->{'_im'}->interlaced('true');
# Put a black frame around the picture
$self->{'_im'}->rectangle( 0, 0,
$self->{'_imx'}-1, $self->{'_imy'}-1,
my $img = Chart::Plot->new;
my $img = Chart::Plot->new ( $image_width, $image_height );
my $anotherImg = new Chart::Plot;
Create a new empty image with the new() method. It will be transparent
and interlaced if your version of GD supports gif format. png does
not yet support either. If image size is not specified, the default is 400
x 300 pixels, or you can specify a different image size. You can also
create more than one image in the same script.
view release on metacpan or search on metacpan
lib/Chart/Base.pm view on Meta::CPAN
$self->{'spaced_bars'} = 'true';
# use the new grey background for the plots
$self->{'grey_background'} = 'true';
# don't default to transparent
$self->{'transparent'} = 'false';
# default to "normal" x_tick drawing
$self->{'x_ticks'} = 'normal';
# we're not a component until Chart::Composite says we are
lib/Chart/Base.pm view on Meta::CPAN
# @return status
sub _set_colors {
my $self = shift;
my $index = $self->_color_role_to_index('background'); # allocate GD color
if ( $self->true( $self->{'transparent'} ) )
{
$self->{'gd_obj'}->transparent($index);
}
# all other roles are initialized by calling $self->_color_role_to_index(ROLENAME);
# and return
lib/Chart/Base.pm view on Meta::CPAN
}
# create the new image
$brush = GD::Image->new( $radius * 2, $radius * 2 );
# get the colors, make the background transparent
$white = $brush->colorAllocate( 255, 255, 255 );
$newcolor = $brush->colorAllocate(@rgb);
$brush->transparent($white);
# draw the circle
if ( $type eq 'line' ) {
$brush->arc( $radius - 1, $radius - 1, $radius, $radius, 0, 360, $newcolor );
$brush->fill( $radius - 1, $radius - 1, $newcolor );
lib/Chart/Base.pm view on Meta::CPAN
if ( grep { $brushStyle eq $_ } ( 'default', 'circle', 'donut', 'OpenCircle', 'FilledCircle' ) ) {
$brush->arc( $xc, $yc, $radius, $radius, 0, 360, $newcolor );
$brush->fill( $xc, $yc, $newcolor );
# draw a white (and therefore transparent) circle in the middle
# of the existing circle to make the "donut", if appropriate
if ( $brushStyle eq 'donut' || $brushStyle eq 'OpenCircle' )
{
$brush->arc( $xc, $yc, int( $radius / 2 ), int( $radius / 2 ), 0, 360, $white );