view release on metacpan or search on metacpan
lib/AAC/Pvoice/Bitmap.pm view on Meta::CPAN
my $rc = $img->Read($file);
carp "Can't read $file: $rc" if $rc;
# wmf files have a white background color by default
# if we can't get the matte color for the image, we assume
# that white can be used as the transparent color...
$img->Transparent(color => 'white') if (!$img->Get('matte') || $file =~ /wmf$/i);
my $w = $img->Get('width');
my $h = $img->Get('height');
my $ch = $textheight;
if (($w > $x) || ($h > ($y-$ch)))
view release on metacpan or search on metacpan
lib/ACME/QuoteDB.pm view on Meta::CPAN
$ENV{ACME_QUOTEDB_PASS} = 'acme';
}
Set the above in a begin block.
The database connection is transparent.
Module usage wise, all operations are the same but now
you will be writing to the remote mysql database specified.
(The user will need read/write permissions to the db/tables)
view release on metacpan or search on metacpan
lib/AI/Genetic/Pro.pm view on Meta::CPAN
logo_position => 'BR',
legend_placement => 'RT',
bgclr => 'white',
boxclr => '#FFFFAA',
transparent => 0,
title => ($params{'-title'} || q/Evolution/ ),
x_label => ($params{'-x_label'} || q/Generation/),
y_label => ($params{'-y_label'} || q/Value/ ),
view release on metacpan or search on metacpan
maint/process-capi.pl view on Meta::CPAN
(?<name>\w+) \s+
\k<name> \s*
;
)
|
(?<transparent>
^
typedef \s+
struct \s+
(?<name>\w+) \s+
\{
view release on metacpan or search on metacpan
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format, SGML
or XML using a publicly available DTD, and standard-conforming simple
HTML, PostScript or PDF designed for human modification. Examples of
transparent image formats include PNG, XCF and JPG. Opaque formats
include proprietary formats that can be read and edited only by
proprietary word processors, SGML or XML for which the DTD and/or
processing tools are not generally available, and the
machine-generated HTML, PostScript or PDF produced by some word
processors for output purposes only.
view release on metacpan or search on metacpan
lib/ALPM/Conf.pod view on Meta::CPAN
not familiar, you can give import arguments the following ways:
# Using use:
use ALPM::Conf '/etc/pacman.conf';
# Require is more transparent:
require ALPM::Conf;
ALPM::Conf->import('/etc/pacman.conf');
# On the command-line (see perlrun(1) manpage):
perl -MALPM::Conf=/etc/pacman.conf -e '...'
view release on metacpan or search on metacpan
doc/code.html view on Meta::CPAN
A:hover { color: #FFFFFF; text-decoration: none; background-color: #6699CC; }
A.noDec:link { color: #000099; font-weight: bold; text-decoration: none; }
A.noDec:visited { color: #000099; font-weight: bold; text-decoration: none; }
A.noDec:active { color: #000099; font-weight: bold; text-decoration: none; }
A.noDec:hover { color: #3366AA; font-weight: bold; text-decoration: underline; background-color: transparent; }
A.plain:link { color: #000033; text-decoration: none; }
A.plain:visited { color: #000033; text-decoration: none; }
A.plain:active { color: #000033; text-decoration: none; }
A.plain:hover { color: #3366AA; text-decoration: none; background-color: transparent; }
h2 {
color: #333333;
font-size: 20 px;
font-weight: bold;
view release on metacpan or search on metacpan
(JCM) bug fix (Ian Flanigan) for perl_ARIndexStruct()
(JCM) modified GetListEntry(), GetEntry(), SetEntry() and
DeleteEntry() to make operations on join schemas
transparent.
(JCM) added a ARVerifyUser call to ars_Login so that
ars_Login() || die() will work as one would expect it to.
(JCM) added $VERSION to the perl module file.
view release on metacpan or search on metacpan
applications/collector-test.pl view on Meta::CPAN
$layer->addDataSet(\@dataOffline, $COLORSRRD {OFFLINE}, " Offline");
# Set the sub-bar gap to 0, so there is no gap between stacked bars with a group
$layer->setBarGap(-1.7E-100, 0);
# Set the bar border to transparent
if ($withBorder) {
$layer->setBorderColor(0xF0F0F0);
} else {
$layer->setBorderColor($perlchartdir::Transparent);
}
view release on metacpan or search on metacpan
$flag ? \@args : @args;
}
=head2 param EXPR [, EXPR]
Simplifies parameter access and makes switch from GET to POST transparent.
Given the following querystring:
myscript.asp?x=a&x=b&y=c
view release on metacpan or search on metacpan
lib/AWS/Lambda/Quick.pm view on Meta::CPAN
=back
And then debug all the above things, a lot, and google weird error
messages it generates when you inevitably make a mistake.
This module provides a way to do all of this completely transparently
just by executing your script, without having to either interact with
the AWS Management Console nor directly use the awscli utility.
Simply include this module at the top of your script containing the
handler function:
view release on metacpan or search on metacpan
Ace/Graphics/Glyph/group.pm view on Meta::CPAN
my ($left,$top) = @_;
# bail out if this isn't the right kind of feature
my @parts = $self->members;
# three pixels of black, three pixels of transparent
my $black = 1;
my ($x1,$y1,$x2,$y2) = $parts[0]->calculate_boundaries($left,$top);
my $center1 = ($y2 + $y1)/2;
view release on metacpan or search on metacpan
devdata/https_mojolicious.io_blog_2017_12_11_day-11-useragent-content-generators view on Meta::CPAN
</code></pre>
<p>Though you have to form the parts a little more manually (no, generators don't call other generators), this is still a much simpler use than building the message manually.
Most notably, the length calculations and all of the boundary handling is done transparently.</p>
<h2>Adding New Content Generators</h2>
<p>So if you are reading this and thinking that Content Generators look great but the type you need isn't available, take heart!
Adding content generators is easy too!
view release on metacpan or search on metacpan
{
$tex .= pack "C", 128; # Give our dot an anti-aliased edge.
}
else
{
$tex .= pack "C", 0; # Outside of the dot, it's transparent.
}
}
}
$Tex_Pixels = OpenGL::Array->new_scalar(GL_UNSIGNED_BYTE,$tex,length($tex));
glDisable(GL_LIGHTING);
# We don'$t want depth-testing either.
glDisable(GL_DEPTH_TEST);
# But, for fun, let's make the text partially transparent too.
glColor4f(0.6,1.0,0.6,.75);
$buf = sprintf "TIME TO EXIT: %.1fs", $time_to_exit;
my $bufwidth = 6 * length $buf;
glRasterPos2i($Window_Width-4-$bufwidth,2); ourPrintString(GLUT_BITMAP_HELVETICA_12,$buf);
view release on metacpan or search on metacpan
lib/Acme/SList/XSLT.pm view on Meta::CPAN
__END__
=head1 NAME
Acme::SList::XSLT - Perform XSLT transparently between XML::LibXSLT and Win32::MinXSLT
=head1 SYNOPSIS
use Acme::SList::XSLT;
view release on metacpan or search on metacpan
lib/Acme/SaBalTongMun.pm view on Meta::CPAN
my $image = GD::Image->new($width, $height);
my $white = $image->colorAllocate( _get_rgb("#FFFFFF") );
my $black = $image->colorAllocate( _get_rgb("#000000") );
# make the background transparent and interlaced
$image->transparent( _get_rgb("#FFFFFF") );
$image->interlaced('true');
my $dest_angle = 0;
for my $string ( @{$self->people} ) {
my $dest_x = $cx + ( $self->radius * cos $dest_angle );
view release on metacpan or search on metacpan
local/lib/perl5/IO/Async/Internals/TimeQueue.pm view on Meta::CPAN
{
my $self = shift;
return $self->val->{code};
}
# This only uses methods so is transparent to HASH or ARRAY
sub cmp
{
my $self = shift;
my $other = shift;
view release on metacpan or search on metacpan
B<Output:> Nothing (for the time being). C<die()>s (C<croak($!)> really) if something goes wrong.
=cut
#todo: use openstr() as in readfile(), transparently gzip .gz filenames and so on
sub writefile {
my($filename,$text)=@_;
if(ref($filename) eq 'ARRAY'){
writefile(@$_) for @$filename;
return;
view release on metacpan or search on metacpan
public/doc/bg/img/default_admin_screen.epz view on Meta::CPAN
<?xml version="1.0"?>
<Document xmlns="http://www.evolus.vn/Namespace/Pencil"><Properties/><Pages><Page><Properties><Property name="name">Untitled Page</Property><Property name="id">1391472647609_5759</Property><Property name="width">980</Property><Property name="height">...
]]></p:property><p:property name="textFont"><![CDATA[Arial|normal|normal|13px|none]]></p:property><p:property name="textColor"><![CDATA[#000000FF]]></p:property><p:property name="textAlign"><![CDATA[1,1]]></p:property></p:metadata>
<defs>
<linearGradient x1="0%" y1="0%" x2="0%" y2="100%" p:name="linearFill" id="36be4582de964e90968b9d4a8d0823fa">
<stop style="stop-color: rgb(192, 192, 192); stop-opacity: 1;" offset="0" p:name="stop1" id="97ba4839a4a8438c832d3b69c28106b0"/>
view release on metacpan or search on metacpan
lib/Agent/TCLI/Transport/Base.pm view on Meta::CPAN
This object method is used by transports to prepare a request for transmssion.
Currently the code is taking a lazy approach and using Perl's YAML and OIO->dump to
safely freeze and thaw the request/responses for Internet transport.
By standardizing these routines in the Base class, more elegant methods
may be transparently enabled in the future.
=cut
# TODO review XEP on this, esp version numbers and best practices.
sub PackRequest {
view release on metacpan or search on metacpan
Thread.readme view on Meta::CPAN
Thread Suppport
---------------
Agent threads are still considered alpha at the moment. So far, they have
worked for me, but I haven't done anything complicated with them yet. :)
I would _like_ to make sending and recieving messages near-transparent by,
for example, having a queue of incoming/outgoing messages, assigning one
thread to handle all incoming data and another to handle all outgoing.
And I've got some other ideas too, but they are all just dreams at the
moment.
view release on metacpan or search on metacpan
examples/rock_paper_scissors.pl view on Meta::CPAN
In general, it's more interesting to evolve "thinking" strategies for Rock,
Paper, Scissors (or any game), than just a fixed sequence of moves. Such
strategies include state machines and genetic programming structures.
Hopefully, though, this example illustrates the ease with which you could
transparently swap in a different type of strategy for this game.
view release on metacpan or search on metacpan
lib/Algorithm/GaussianElimination/GF2.pm view on Meta::CPAN
=item $eq->len
Returns the internal length of the coeficients vector.
Note that this value is just a hint as the internal representation
grows transparently when new coeficients are set or inside the
C<solve> method.
=back
=head1 SEE ALSO
view release on metacpan or search on metacpan
- SVM: Added binding for predict_values, improved memory usage
- DataSet: changed to use sparse format internally
internal format similar to what libsvm uses
added asArray function, improved memory usage
- All changes (except libsvm update which slightly changes the
learned models) are completely transparent to the user. No
changes in programs depending on this should be necessary.
0.13 Tue Jan 22 13:38:00 PDT 2008
- Updated the underlaying libsvm version to 2.85
view release on metacpan or search on metacpan
share/static/alice-dark.css view on Meta::CPAN
li.monospaced div.msg {
padding: 7px 5px; }
li.event + li.message div.msg {
border-top: 1px solid transparent; }
ul.messages li:first-child div.msg {
border-top: 1px solid transparent; }
/* so the last avatar doesn't hang off the edge */
ul.messages li.avatar:not(.consecutive) div.msg {
min-height: 35px; }
view release on metacpan or search on metacpan
src/Source/FreeImage.h view on Meta::CPAN
// RescaleEx options ---------------------------------------------------------
// Constants used in FreeImage_RescaleEx
#define FI_RESCALE_DEFAULT 0x00 //! default options; none of the following other options apply
#define FI_RESCALE_TRUE_COLOR 0x01 //! for non-transparent greyscale images, convert to 24-bit if src bitdepth <= 8 (default is a 8-bit greyscale image).
#define FI_RESCALE_OMIT_METADATA 0x02 //! do not copy metadata to the rescaled image
#ifdef __cplusplus
extern "C" {
view release on metacpan or search on metacpan
doc/html/CustomButtons.html view on Meta::CPAN
background:none;
border:none;
cursor:pointer;
padding:1px 2px;
color:#000;
background-color:transparent !important;
}
.gva-btn-container .btn {float:left;}
.gva-btn-container.btn-focus .btn {color:#aa0000;}
.gva-btn-container span {display:block;float:left;height:21px;}
.gva-btn-container span.left {background:transparent url(btn_sprite.gif) no-repeat scroll 0 0;padding:0 1px 0 2px;margin-left:4px;}
.gva-btn-container span.center {background:transparent url(btn_sprite.gif) repeat-x scroll 0 -42px;padding:0 2px}
.gva-btn-container span.right {background:transparent url(btn_sprite.gif) no-repeat scroll 0 -21px;padding:0 1px 0 2px;}
.gva-btn-container.btn-hover span.left {background-position:0 -63px;}
.gva-btn-container.btn-hover span.center {background-position:0 -105px;}
.gva-btn-container.btn-hover span.right {background-position:0 -84px;}
.gva-btn-container.btn-focus span.left {background-position:0 -63px;}
.gva-btn-container.btn-focus span.center {background-position:0 -126px;}
view release on metacpan or search on metacpan
lib/Alien/Hush.pm view on Meta::CPAN
Alien::Hush - Easily find or install the Hush cryptocoin full node
=head1 DESCRIPTION
Hush is a privacy coin that is the grandchild of Bitcoin and the
daughter of Zcash. In addition to *transparent* taddr's from the
Bitcoin world, there is now *shielded* addresses called zaddr's,
which are protected by Zero Knowledge mathematics known as zkSNARKs.
Learn more at the official Hush website: https://myhush.org
view release on metacpan or search on metacpan
src/judy-1.0.5/src/JudyCommon/JudyPrivate.h view on Meta::CPAN
//
// In these macros, "i_offset" is an index offset, and "b_off" is a byte
// offset for odd Index sizes.
//
// Note: Endian issues only arise fro insertion, not deletion, and even for
// insertion, they are transparent when native (even) objects are used, and
// handled explicitly for odd (non-native) Index sizes.
//
// Note: The following macros are tricky enough that there is some test code
// for them appended to this file.
view release on metacpan or search on metacpan
libjit/attic/jit-rules-alpha.h view on Meta::CPAN
*
* All memory access on alpha must be naturally aligned. There are
* unaligned load and store instructions to operate on arbitrary byte
* boundaries. However sometimes compilers don't always spot where
* to use them due to programming tricks with pointers. The kernel will
* do the fetch transparently if the access is unaligned and not done
* with the proper instructions. Kernel assisted unaligned accesses
* don't change the behavior of the program.
*
* TODO: benchmark this to determine what is more costly... setting
* up everything to be aligned or dealing with the unaligned accesses.