view release on metacpan or search on metacpan
t/Data/Test/Tech.pm view on Meta::CPAN
}
#########
# References to arrays and scalars in the config may
# be transparent.
#
my $current_value = $key_p->{$key};
if( ref($current_value) eq 'SCALAR') {
$current_value = $$current_value;
}
t/Data/Test/Tech.pm view on Meta::CPAN
The C<tech_config> subroutine always returns the
C<$old_value> of C<$dot_index> and only writes
the contents if C<$new_value> is defined.
The 'SCALAR' and 'ARRAY' references are transparent.
The C<tech_config> subroutine, when it senses that
the C<$dot_index> is for a 'SCALAR' and 'ARRAY' reference,
will read or write the contents instead of the reference.
The The C<tech_config> subroutine will read 'HASH" references
view release on metacpan or search on metacpan
lib/Data/Transform.pm view on Meta::CPAN
A flag method that always returns 1. This can be used in e.g. POE to check
if the class supports L<Data::Transform::Meta>, which all Data::Transform
subclasses should, but L<POE::Filter> classes don't. Doing it this way
instead of checking if a filter is a Data::Transform subclass allows for
yet another filters implementation that is meant to transparently replace
this to be used by POE without changes to POE.
=cut
sub meta {
view release on metacpan or search on metacpan
eg/lindenmayer-gd view on Meta::CPAN
my %color = (
white => $img->colorAllocate( 255, 255, 255 ),
black => $img->colorAllocate( 0, 0, 0 ),
);
$img->transparent( $color{white} );
$img->interlaced('true');
my @statestack;
my %translate = (
view release on metacpan or search on metacpan
lib/Data/YAML.pm view on Meta::CPAN
=head1 DESCRIPTION
In the spirit of L<YAML::Tiny>, L<Data::YAML::Reader> and
L<Data::YAML::Writer> provide lightweight, dependency-free YAML
handling. While C<YAML::Tiny> is designed principally for working with
configuration files C<Data::YAML> concentrates on the transparent round-
tripping of YAML serialized Perl data structures.
As an example of why this distinction matters consider that
C<YAML::Tiny> doesn't handle hashes with keys containing non-printable
characters. This is fine for configuration files but likely to cause
view release on metacpan or search on metacpan
dw-nav will create the base of a simple Data Warehouse Navigator.
=head2 AGGREGATE NAVIGATOR
One of the main features of the Data Warehouse Navigator is the
transparent Aggregate Navigator.
The Aggregate Navigator will intercept SQL queries and generate
aggregate tables, whenever is possible.
The use of aggregate tables can speed up Data Warehouse by 100s
view release on metacpan or search on metacpan
lib/Date/Calc/Object.pod view on Meta::CPAN
=item *
Languages
Note that this module is completely transparent to the setting
of a language in "Date::Calc". This means that you can choose a
language in "Date::Calc" (with the "Language()" function) and all
dates subsequently printed by this module will automatically be
in that language - provided that you use the built-in formats of
this module, or that you pass the third parameter of the callback
view release on metacpan or search on metacpan
lib/Date/Pcalc/Object.pod view on Meta::CPAN
=item *
Languages
Note that this module is completely transparent to the setting
of a language in "Date::Pcalc". This means that you can choose a
language in "Date::Pcalc" (with the "Language()" function) and all
dates subsequently printed by this module will automatically be
in that language - provided that you use the built-in formats of
this module, or that you pass the third parameter of the callback
view release on metacpan or search on metacpan
going between and two arbitrary formats foo and bar, the function only
needs to convert foo to the base class and the base class to bar. Ie:
Gregorian <--> Base class <--> Hebrew
The base class includes a B<Convert> method to do this transparently.
Nothing is exported because it wouldn't make any sense to export. :)
=head1 DESCRIPTION
view release on metacpan or search on metacpan
(addition and subtraction), and provides many convenient methods
for retrieving portions of a date/time.
This module properly supports the Olson time zone database, meaning
that historical time zone information, and more importantly, daylight
saving time rules, can be handled transparently, simply by setting the
correct time zone. This is done by using the DateTime::TimeZone
module.
INSTALLATION
view release on metacpan or search on metacpan
examples/web/reset.css view on Meta::CPAN
padding: 0;
border: 0;
outline: 0;
font-size: 100%;
vertical-align: baseline;
background: transparent;
}
body {
line-height: 1;
}
ol, ul {
view release on metacpan or search on metacpan
Docs/Debug-Fork-Tmux-Config.html view on Meta::CPAN
margin: 0;
padding: 1ex;
}
A:link, A:visited {
background: transparent;
color: #006699;
}
A[href="#POD_ERRORS"] {
background: transparent;
color: #FF0000;
}
DIV {
border-width: 0;
Docs/Debug-Fork-Tmux-Config.html 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;
}
view release on metacpan or search on metacpan
2.10 Fri Jan 15 16:14:02 CET 2010
- fix blending factors to avoid white-out when fow_intensity > 0.
2.09 Tue Dec 22 01:40:24 CET 2009
- implement smooth fow/lighting transitions by blending.
- make fow texture configurable and add stipple/transparent versions.
- empty "Host" field will now default to gameserver.deliantra.net.
- do not crash when the user enters an invalid value into "Host".
- fix positional rounding on (pre-c99) windows.
- use a pack/unpack alignment of 1 by default everywhere, drop alignment
code in fow_texture.
view release on metacpan or search on metacpan
lib/Dev/Bollocks.pm view on Meta::CPAN
slick
sticky
strategic
synergistic
third-generation
transparent
total
turn-key
ubiquitous
unique
user-centric
view release on metacpan or search on metacpan
}
}
return @bkptIDs;
}
# I try to make the types transparent, but we need to give a typemap
# anyway
sub emitTypeMapInfo($$) {
my ($cmd, $transactionID) = @_;
my $res = sprintf(qq(%s\n<response %s %s %s command="%s"
view release on metacpan or search on metacpan
DebugInit.pm view on Meta::CPAN
Debugger initialization files can contain user-defined functions that
make doing complicated or repetitive actions easier. Normally, from
within the debugger a user can evaluate any C function call. But for a
number of reasons, many projects use C preprocessor macros (#define
statements) in place of an actual C function call. The use of macros
instead of function calls is transparent during compilation, but most
debuggers do not allow access to macros, and so the user must type in
the code by hand each time s/he wants to use a macro, or must build an
initialization file by hand. Retyping is tedious, but hand coding the
initialization file may result in antiquated code when the project changes. By
automating the process, I hope to alleviate a few headaches for
view release on metacpan or search on metacpan
bin/perlbrewise-spec view on Meta::CPAN
funny/weird/dumb stuff).
This is useful when you want to do the encoding yourself (e.g. when you
want to have UTF-16 encoded JSON texts) or when some other layer does
the encoding for you (for example, when printing to a terminal using a
filehandle that transparently encodes to UTF-8 you certainly do NOT want
to UTF-8 encode your data first and have Perl encode it another time).
=item C<utf8> flag enabled
If the C<utf8>-flag is enabled, C<encode>/C<decode> will encode all
view release on metacpan or search on metacpan
subr_entry->initial_overhead_ticks = cumulative_overhead_ticks;
subr_entry->initial_subr_ticks = cumulative_subr_ticks;
subr_entry->subr_call_seqn = (unsigned long)(++cumulative_subr_seqn);
/* try to work out what sub's being called in advance
* mainly for xsubs because otherwise they're transparent
* because xsub calls don't get a new context
*/
if (op_type == OP_ENTERSUB || op_type == OP_GOTO) {
GV *called_gv = Nullgv;
subr_entry->called_cv = resolve_sub_to_cv(aTHX_ subr_sv, &called_gv);
view release on metacpan or search on metacpan
classdocs/podstyle.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;
classdocs/podstyle.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;
classdocs/podstyle.css view on Meta::CPAN
padding: 0.5ex 1ex;
vertical-align: baseline;
}
.path A {
background: transparent;
color: #006699;
font-weight: bold;
}
.pages {
classdocs/podstyle.css view on Meta::CPAN
margin: 1ex 0;
padding: 1px;
}
.menubar .links {
background: transparent;
color: white;
padding: 0.2ex;
text-align: left;
}
classdocs/podstyle.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 {
classdocs/podstyle.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 {
classdocs/podstyle.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 {
classdocs/podstyle.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
classdocs/podstyle.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;
classdocs/podstyle.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;
classdocs/podstyle.css view on Meta::CPAN
padding: 0.5ex 1ex;
vertical-align: baseline;
}
.path A {
background: transparent;
color: #006699;
font-weight: bold;
}
.pages {
classdocs/podstyle.css view on Meta::CPAN
margin: 1ex 0;
padding: 1px;
}
.menubar .links {
background: transparent;
color: white;
padding: 0.2ex;
text-align: left;
}
classdocs/podstyle.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 {
classdocs/podstyle.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 {
classdocs/podstyle.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 {
classdocs/podstyle.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/Devel/SizeMe/Graph/static/bootstrap/css/bootstrap-responsive.css view on Meta::CPAN
clear: both;
}
.hide-text {
font: 0/0 a;
color: transparent;
text-shadow: none;
background-color: transparent;
border: 0;
}
.input-block-level {
display: block;
lib/Devel/SizeMe/Graph/static/bootstrap/css/bootstrap-responsive.css view on Meta::CPAN
display: none;
float: none;
max-width: none;
padding: 0;
margin: 0 15px;
background-color: transparent;
border: none;
-webkit-border-radius: 0;
-moz-border-radius: 0;
border-radius: 0;
-webkit-box-shadow: none;
view release on metacpan or search on metacpan
lib/Devel/Spy.pm view on Meta::CPAN
Devel::Spy - Spy on your objects and data
=head1 DESCRIPTION
Devel::Spy is a transparent wrapper over your objects and data. All
accesses are logged. This is useful for instrumenting "black box"
code. You can just look at see what the code used and how it used it.
I used it to find out what attributes and values were being used as
booleans and then wrote tests that fed the "black box" code with
lib/Devel/Spy.pm view on Meta::CPAN
=over
=item C<< WRAPPED THING = Devel::Spy->new( THING, LOGGING FUNCTION ) >>
Wraps a thing in a transparent proxy object. This is how you
instrument your things.
=item C<< ( ARRAY REF, LOGGING FUNCTION ) = Devel::Spy->make_eventlog >>
Returns an array reference and a logging function. Pass the logging
view release on metacpan or search on metacpan
lib/Devel/hdb/html/bootstrap.css view on Meta::CPAN
* Copyright 2012 Twitter, Inc
* Licensed under the Apache License v2.0
* http://www.apache.org/licenses/LICENSE-2.0
*
* Designed and built with all the love in the world @twitter by @mdo and @fat.
*/.clearfix{*zoom:1}.clearfix:before,.clearfix:after{display:table;line-height:0;content:""}.clearfix:after{clear:both}.hide-text{font:0/0 a;color:transparent;text-shadow:none;background-color:transparent;border:0}.input-block-level{display:block;wi...
view release on metacpan or search on metacpan
presentation/scripts/dd_roundies.js view on Meta::CPAN
*
* Just want the PNG fixing effect for IE6, and don't want to also use the DD_belatedPNG library? Don't give any additional arguments after the CSS selector.
* DD_roundies.addRule('.your .example img');
**/
eval(function(p,a,c,k,e,r){e=function(c){return(c<a?'':e(parseInt(c/a)))+((c=c%a)>35?String.fromCharCode(c+29):c.toString(36))};if(!''.replace(/^/,String)){while(c--)r[e(c)]=k[c]||e(c);k=[function(e){return r[e]}];e=function(){return'\\w+'};c=1};whil...
view release on metacpan or search on metacpan
lib/Device/HID.pm view on Meta::CPAN
=item renew_on_timeout
$dev->renew_on_timeout;
Closes HIDAPI handle and opens a new one transparently at C<read_data> timeout and retries reading. When C<read_data> returns successfully the first time, C<renew_on_timeout> is reset and timeout is set to C<undef>, but can be manually adjusted.
For reasons unknown to me, Valve's Steam controller needs a couple of C<hid_open> calls before C<hid_read> manages to read data. None of the prior C<hid_open> calls fail, they just block indefinitely. For devices that ought to report periodically wha...
=cut
view release on metacpan or search on metacpan
lib/Device/Serdisp.pm view on Meta::CPAN
# reserves a color-indexed picture
my $image = GD::Image->new(128,64);
my $black = $image->colorAllocate(0,0,0);
my $white = $image->colorAllocate(255,255,255);
$image->transparent($black);
$image->arc(10,10,10,10,0,270, $white);
$d->copyGD($image);
=head1 DESCRIPTION
view release on metacpan or search on metacpan
SerialPort.pm view on Meta::CPAN
is not altered). The B<streamline> choice allows duplicating the operation
of Win32::SerialPort for cross-platform scripts.
The implementation attempts to mimic STDIN/STDOUT behaviour as closely
as possible: calls block until done and data strings that exceed internal
buffers are divided transparently into multiple calls. In Version 0.06,
the output separators C<$,> and C<$\> are also applied to PRINT if set.
The B<output_record_separator> and B<output_field_separator> methods can set
I<Port-FileHandle-Specific> versions of C<$,> and C<$\> if desired. Since
PRINTF is treated internally as a single record PRINT, C<$\> will be applied.
Output separators are not applied to WRITE (called as
view release on metacpan or search on metacpan
lib/Dezi/Aggregator/Spider/UA.pm view on Meta::CPAN
use Search::Tools::UTF8;
use Dezi::Aggregator::Spider::Response;
our $VERSION = '0.016';
# if Compress::Zlib is installed, this should handle gzip transparently.
# thanks to
# http://stackoverflow.com/questions/1285305/how-can-i-accept-gzip-compressed-content-using-lwpuseragent
my $can_accept = HTTP::Message::decodable();
# TODO handle when Zlib is *not* installed, via Content-Encoding header
view release on metacpan or search on metacpan
lib/Debian/Control/Stanza/Binary.pm view on Meta::CPAN
=item long_description
=back
Setting them transparently modifies I<Description>. Note that the value of
I<long_description> is "unmangled", that is without leading spaces, and empty
lines are empty. I<Description> on the other hand is just as it looks in a
regular debian/control file - the long part is indented with a single space and
empty lines are replaced with dots.
view release on metacpan or search on metacpan
share/htdocs/index.ttk view on Meta::CPAN
</div>
<div id="profileDataChart" style="display:none;"></div>
<div id="profileDataPopup" title="Popup dialog" style="display:none;"></div>
</div>
<!--/div.content-->
<span style="font-family:Impact; color:transparent;">t</span>
[% SET html_foot = root_dir _ "html-foot.ttk" %]
[% PROCESS $html_foot linkbar=0 linkttk="dc-links.ttk" %]
<script type="text/javascript">ttk_elapsed = [% cdb.t_elapsed.json %];</script>
</div>
<!--/div.outer-->
view release on metacpan or search on metacpan
DiaColloDB/Utils.pm view on Meta::CPAN
}
## \&filter_sub = PACKAGE::packFilterStore($pack_template)
## \&filter_sub = PACKAGE::packFilterStore([$pack_template_store, $pack_template_fetch])
## \&filter_sub = PACKAGE::packFilterStore([\&pack_code_store, \&pack_code_fetch])
## + returns a DB_File-style STORE-filter sub for transparent packing of data to $pack_template
sub packFilterStore {
my $that = UNIVERSAL::isa($_[0],__PACKAGE__) ? shift : __PACKAGE__;
my $packas = shift;
$packas = $packas->[0] if (UNIVERSAL::isa($packas,'ARRAY'));
return $packas if (UNIVERSAL::isa($packas,'CODE'));
DiaColloDB/Utils.pm view on Meta::CPAN
}
## \&filter_sub = PACKAGE::packFilterFetch($pack_template)
## \&filter_sub = PACKAGE::packFilterFetch([$pack_template_store, $pack_template_fetch])
## \&filter_sub = PACKAGE::packFilterFetch([\&pack_code_store, \&pack_code_fetch])
## + returns a DB_File-style FETCH-filter sub for transparent unpacking of data from $pack_template
sub packFilterFetch {
my $that = UNIVERSAL::isa($_[0],__PACKAGE__) ? shift : __PACKAGE__;
my $packas = shift;
$packas = $packas->[1] if (UNIVERSAL::isa($packas,'ARRAY'));
return $packas if (UNIVERSAL::isa($packas,'CODE'));