view release on metacpan or search on metacpan
lib/Dancer/Session/JSON.pm view on Meta::CPAN
=head1 DESCRIPTION
This module implements a session engine based on JSON files. Session are stored
in a I<session_dir> as JSON files. The idea behind this module was to provide a
transparent session storage for the developer.
This backend is intended to be used in development environments, when looking
inside a session can be useful.
It's not recommended to use this session engine in production environments.
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Dancer2/Plugin/Auth/Extensible.pm view on Meta::CPAN
}
}
if ( $plugin->login_without_redirect ) {
# Add a post route so we can catch transparent login.
# This is a little sucky but since no hooks are called before
# route dispatch then adding this wildcard route now does at
# least make sure it gets added before any routes that use this
# plugin's route decorators are added.
lib/Dancer2/Plugin/Auth/Extensible.pm view on Meta::CPAN
'__auth_extensible_method' => lc($request->method) );
$plugin->app->session->write(
'__auth_extensible_params' => \%{ $request->params } );
}
return $plugin->_render_login_page( 'transparent_login.tt', $tokens );
}
# old-fashioned redirect to login page with return_url set
my $forward = $request->path;
$forward .= "?".$request->query_string
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Dancer2/Plugin/LiteBlog/Scaffolder/Data.pm view on Meta::CPAN
.post-meta li.clickable:hover a {
color: #fff; /* Changing text color on hover */
}
.post-meta li.clickable:hover
{
background-color: rgba(255, 165, 0, 0.8); /* transparent orange color */
color: #fff; /* Changing text color on hover */
}
.post-meta li.clickable a:hover {
text-decoration: none; /* Removing underline on hover */
lib/Dancer2/Plugin/LiteBlog/Scaffolder/Data.pm view on Meta::CPAN
margin-top: 0;
box-shadow: 0 4px 6px rgba(0, 0, 0, 0.5); /* Soft shadow for depth */
margin-bottom: 2rem;
background-color: rgba(255, 255, 255, 0.8); /* a semi transparent white */
color: #444;
margin-bottom: 0;
}
lib/Dancer2/Plugin/LiteBlog/Scaffolder/Data.pm view on Meta::CPAN
position: absolute;
top: -4px;
left: 0;
border-width: 5px 5px 0;
border-style: solid;
border-color: #f16522 transparent transparent transparent;
}
.blog-button {
text-align: center;
margin-top: 20px;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Dancer2/Plugin/LogReport/Message.pod view on Meta::CPAN
[2.03] Log messages are/can be stored in the Session object. The Session
object may be cached in a file, in various formats. To be able to save
and restore these message objects from this session serialization, we
need to freeze and thaw the object at the right moment. This happens
transparently.
For session serialization in the database, put this in your
configuration:
engines:
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Dancer2/Plugin/Multilang.pm view on Meta::CPAN
}
elsif...
=head1 USAGE
No language information has to be managed in route definition. Language path will be added transparently to your routes.
language keyword can be used to retrieve language information inside the route manager.
=head1 OPTIONS
view all matches for this distribution
view release on metacpan or search on metacpan
docs/html/Dancer2-Template-TextTemplate-FakeEngine.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/html/Dancer2-Template-TextTemplate-FakeEngine.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 all matches for this distribution
view release on metacpan or search on metacpan
share/assets/dash_core_components/async~datepicker.js view on Meta::CPAN
(window.webpackJsonpdash_core_components=window.webpackJsonpdash_core_components||[]).push([[2],Array(195).concat([function(e,t,n){(function(e){e.exports=function(){"use strict";var t,r;function a(){return t.apply(null,arguments)}function o(e){return...
//# sourceMappingURL=async~datepicker.js.map
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Data/Alias.pm view on Meta::CPAN
Exported by default.
Enables aliasing semantics within the expression or block. Returns an alias
to the expression, or the block's return value.
C<alias> is context-transparent, meaning that whichever context it is placed in
(list, scalar, void), the expression/block is evaluated in the same context.
=head2 copy I<EXPR> | copy I<BLOCK>
Restores normal (copying) semantics within the expression or block, and
makes a copy of the result value (unless in void context).
Like C<alias>, C<copy> is context-transparent.
=head2 deref I<LIST>
Accepts a list of references to scalars, arrays, or hashes. Applies the
applicable dereferencing operator to each. This means that:
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Data/AnyXfer/Elastic/Import/Storage/Directory.pm view on Meta::CPAN
Optional. The temporary directory data should be written to as operations are performed
on this instance.
=item B<item_file_suffix>
Optional. A string that will be appended to the end of every item name transparently
when written to storage (will not be visible through the storage interface).
You can also use this for file extensions.
=item B<item_file_prefix>
Optional. A string that will be prepended to the start of every item name transparently
when written to storage (will not be visible through the storage interface).
=back
=head1 STORAGE INTERFACE
lib/Data/AnyXfer/Elastic/Import/Storage/Directory.pm view on Meta::CPAN
Converts an arbritrary string to a format safe to be used by this storage
backend as an item name.
This is not necessary on storage interface methods as this is handled
transparently for you.
=head3 CAVEATS
This convertion is most likely one-way (lossy). Because of the normalisation,
different strings can point to the same item,
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Data/BitStream/BLVec.pm view on Meta::CPAN
This document only describes the unique features of this implementation,
which is of limited value to people purely using L<Data::BitStream>.
This implementation points everything to the implementations in
Data::BitStream::XS where possible. This gives the majority of the performance
benefit of the XS module, while (1) transparently applying the speedup through
the Data::BitStream package, and (2) allowing all the Moo/Mouse/Moose extensions
and extra roles to be used while still retaining high performance at the core.
This is the default L<Data::BitStream> implementation if Data::BitStream::XS
is installed.
view all matches for this distribution
view release on metacpan or search on metacpan
* @brief Exposes the implementation without marking functions as inline.
*/
# define XXH_PRIVATE_API
# undef XXH_PRIVATE_API
/*!
* @brief Emulate a namespace by transparently prefixing all symbols.
*
* If you want to include _and expose_ xxHash functions from within your own
* library, but also want to avoid symbol collisions with other libraries which
* may also include xxHash, you can use @ref XXH_NAMESPACE to automatically prefix
* any public symbol from xxhash library with the value of @ref XXH_NAMESPACE
view all matches for this distribution
view release on metacpan or search on metacpan
to be operated on. Select() and sort() methods manipulate the
selection list. Later, you can optionally rewrite the table in memory
or on disk to reflect changes in the selection list or field list.
Data::CTable reads and writes any tabular text file format including
Merge, CSV, Tab-delimited, and variants. It transparently detects,
reads, and preserves Unix, Mac, and/or DOS line endings and tab or
comma field delimiters -- regardless of the runtime platform.
In addition to reading data files, CTable is a good way to gather,
store, and operate on tabular data in memory, and to export data to
view all matches for this distribution
view release on metacpan or search on metacpan
* @brief Exposes the implementation without marking functions as inline.
*/
# define XXH_PRIVATE_API
# undef XXH_PRIVATE_API
/*!
* @brief Emulate a namespace by transparently prefixing all symbols.
*
* If you want to include _and expose_ xxHash functions from within your own
* library, but also want to avoid symbol collisions with other libraries which
* may also include xxHash, you can use @ref XXH_NAMESPACE to automatically prefix
* any public symbol from xxhash library with the value of @ref XXH_NAMESPACE
view all matches for this distribution
view release on metacpan or search on metacpan
* @brief Exposes the implementation without marking functions as inline.
*/
# define XXH_PRIVATE_API
# undef XXH_PRIVATE_API
/*!
* @brief Emulate a namespace by transparently prefixing all symbols.
*
* If you want to include _and expose_ xxHash functions from within your own
* library, but also want to avoid symbol collisions with other libraries which
* may also include xxHash, you can use @ref XXH_NAMESPACE to automatically prefix
* any public symbol from xxhash library with the value of @ref XXH_NAMESPACE
view all matches for this distribution
view release on metacpan or search on metacpan
share/modally-1.1.0/jquery.modally.css view on Meta::CPAN
margin: 0;
padding: 0;
overflow: visible;
cursor: pointer;
background: transparent;
position: absolute;
top: 0px;
right: 0px;
padding: 12px 20px;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Data/Dumper/Interp.pm view on Meta::CPAN
$useqq .= ":unicode:controlpics" if delete $mod{c};
$useqq .= ":condense" if delete $mod{C};
$code .= '->Debug(2)' if delete $mod{D};
$useqq .= ":hex" if delete $mod{h};
$code .= '->Objects(0)' if delete $mod{o}; # show internals
$code .= '->Objects({overloads => "transparent"})' if delete $mod{O}; # hide overloaded objects, not even showing classname
$useqq .= ":octets" if delete $mod{B};
$code .= '->Refaddr(1)' if delete $mod{r};
$useqq .= ":underscores" if delete $mod{u};
$code .= "->Useqq(\$Useqq.'${useqq}')" if $useqq ne "";
lib/Data/Dumper/Interp.pm view on Meta::CPAN
$trunctailwidth = min($trunctailwidth//0, $maxstringwidth);
my $ovopt = "tagged";
if (ref($objects) eq "HASH") {
foreach my $key (keys %$objects) {
if ($key eq 'show_classname') { # DEPRECATED
$ovopt = $objects->{$key} ? "tagged" : "transparent"
}
elsif ($key eq 'overloads') {
if (!defined($objects->{$key})) {
$ovopt = "tagged";
}
elsif ($objects->{$key} =~ /^(?:tagged|transparent|ignore)$/) {
$ovopt = $objects->{$key}
}
else { confess "Invalid 'overloads' sub-opt value '$objects->{$key}'" }
}
elsif ($key eq 'objects') { }
lib/Data/Dumper/Interp.pm view on Meta::CPAN
=over
B<overloads =E<gt> "tagged"> (the default): "(classname)" is prepended to the result when an overloaded operator is evaluated.
B<overloads =E<gt> "transparent"> : The overload results
will appear unadorned, i.e. they will look as if the overload result
was the original value.
B<overloads =E<gt> "ignore"> : Overloaded operators are not evaluated at all;
the original object's abbreviated refaddr is shown
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Data/Enumerable/Lazy.pm view on Meta::CPAN
Creates a new enumerable by extending the existing one. on_next is
the only manfatory argument. on_has_next might be overriden if some
custom logic comes into play.
is_finite is inherited from the parent enumerable by default. All additional
attributes would be transparently passed to the constuctor.
=cut
sub continue {
my ($this, $ext) = @_;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Data/Feed/RSS.pm view on Meta::CPAN
$f->{'xml:base'} = shift;
}
return $f->{'xml:base'};
}
## The following all work transparently in any RSS version.
sub language {
my $feed = shift->feed;
if (@_) {
$feed->channel('language', $_[0]);
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Data/HashMap/Shared.pm view on Meta::CPAN
The batch ops (C<set_multi>, C<get_multi>, C<remove_multi>) dispatch each key
to its shard independently rather than holding one lock for the whole call, so
on a sharded map a batch is B<not> atomic across shards (the "single lock"
note in the API below applies to non-sharded maps).
All operations work transparently on sharded maps: C<put>, C<get>, C<remove>,
C<exists>, C<add>, C<update>, C<swap>, C<take>, C<incr>, C<max>, C<min>, C<cas>, C<cas_take>,
C<get_or_set>, C<put_ttl>, C<add_ttl>, C<update_ttl>, C<touch>, C<persist>,
C<set_ttl>, C<keys>, C<values>, C<items>, C<to_hash>, C<set_multi> (method only),
C<remove_multi> (method only), C<get_multi> (method only),
C<get_with_ttl> (method only), C<each>, C<pop>, C<shift>, C<drain>,
view all matches for this distribution
view release on metacpan or search on metacpan
* @brief Exposes the implementation without marking functions as inline.
*/
# define XXH_PRIVATE_API
# undef XXH_PRIVATE_API
/*!
* @brief Emulate a namespace by transparently prefixing all symbols.
*
* If you want to include _and expose_ xxHash functions from within your own
* library, but also want to avoid symbol collisions with other libraries which
* may also include xxHash, you can use @ref XXH_NAMESPACE to automatically prefix
* any public symbol from xxhash library with the value of @ref XXH_NAMESPACE
view all matches for this distribution
view release on metacpan or search on metacpan
* @brief Exposes the implementation without marking functions as inline.
*/
# define XXH_PRIVATE_API
# undef XXH_PRIVATE_API
/*!
* @brief Emulate a namespace by transparently prefixing all symbols.
*
* If you want to include _and expose_ xxHash functions from within your own
* library, but also want to avoid symbol collisions with other libraries which
* may also include xxHash, you can use @ref XXH_NAMESPACE to automatically prefix
* any public symbol from xxhash library with the value of @ref XXH_NAMESPACE
view all matches for this distribution
view release on metacpan or search on metacpan
doc/rfc2445.txt view on Meta::CPAN
CATEGORIES:BUSINESS,HUMAN RESOURCES
END:VEVENT
The following is an example of the "VEVENT" calendar component used
to represent a reminder that will not be opaque, but rather
transparent, to searches for busy time:
BEGIN:VEVENT
UID:19970901T130000Z-123402@host.com
DTSTAMP:19970901T1300Z
DTSTART:19970401T163000Z
doc/rfc2445.txt view on Meta::CPAN
calendar date.
The "VJOURNAL" calendar component does not take up time on a
calendar. Hence, it does not play a role in free or busy time
searches - - it is as though it has a time transparency value of
TRANSPARENT. It is transparent to any such searches.
The "VJOURNAL" calendar component cannot be nested within another
calendar component. However, "VJOURNAL" calendar components can be
related to each other or to a "VEVENT" or to a "VTODO" calendar
component, with the "RELATED-TO" property.
doc/rfc2445.txt view on Meta::CPAN
4.8.2.7 Time Transparency
Property Name: TRANSP
Purpose: This property defines whether an event is transparent or not
to busy time searches.
Value Type: TEXT
Property Parameters: Non-standard property parameters can be
doc/rfc2445.txt view on Meta::CPAN
transvalue = "OPAQUE" ;Blocks or opaque on busy time searches.
/ "TRANSPARENT" ;Transparent on busy time searches.
;Default value is OPAQUE
Example: The following is an example of this property for an event
that is transparent or does not block on free/busy time searches:
TRANSP:TRANSPARENT
The following is an example of this property for an event that is
opaque or blocks on free/busy time searches:
view all matches for this distribution
view release on metacpan or search on metacpan
* @brief Exposes the implementation without marking functions as inline.
*/
# define XXH_PRIVATE_API
# undef XXH_PRIVATE_API
/*!
* @brief Emulate a namespace by transparently prefixing all symbols.
*
* If you want to include _and expose_ xxHash functions from within your own
* library, but also want to avoid symbol collisions with other libraries which
* may also include xxHash, you can use @ref XXH_NAMESPACE to automatically prefix
* any public symbol from xxhash library with the value of @ref XXH_NAMESPACE
view all matches for this distribution
view release on metacpan or search on metacpan
Locations.pm view on Meta::CPAN
You can also think of "C<Data::Locations>" as bubbles and bubbles inside
of other bubbles. You can inflate these bubbles in any arbitrary order
you like through a straw (i.e., the bubble's object reference).
Note that this module handles your data completely transparently, which
means that you can use it equally well for text AND binary data.
You might also be interested in knowing that this module and its concept
have already been heavily used in the automatic code generation of large
software projects.
view all matches for this distribution
view release on metacpan or search on metacpan
msgpack-3.3.0/Doxyfile view on Meta::CPAN
# code bases. Also note that the size of a graph can be further restricted by
# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
MAX_DOT_GRAPH_DEPTH = 0
# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
# background. This is disabled by default, because dot on Windows does not
# seem to support this out of the box. Warning: Depending on the platform used,
# enabling this option may lead to badly anti-aliased labels on the edges of
# a graph (i.e. they become hard to read).
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Data/Miscellany.pm view on Meta::CPAN
=head2 is_defined(SCALAR)
A kind of C<defined()> that is aware of L<Class::Value>, which has its own
views of what is a defined value and what isn't. The issue arose since
L<Class::Value> objects are supposed to be used transparently, mixed with
normal scalar values. However, it is not possible to overload "definedness",
and C<defined()> used on a value object always returns true since the
object reference certainly exists. However, what we want to know is
whether the value encapsulated by the value object is defined.
Additionally, each value class can have its own ideas of when its
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Data/MuFormX/Registry.pm view on Meta::CPAN
classes. At its heart it makes it so you don't have to say 'use Form;' for
every form you need in a package. It also adds a way to centralize some
form initialization work. This may or may not recommend itself to you. I
think it makes it easier to reuse forms in different packages (for example in
different L<Mojolicous> controllers). On the other hand it injects a proxy
layer such that '$registry->create("Login")' is not 100% transparent in that
you are getting an instance of 'MyApp::Form::Login'. You may consider this
a type of action at a distance that makes your code harder to maintain.
If you have a lot of L<Data::MuForm> based form validation classes you may find
it more useful. I also believe it helps you follow the 'code against an interface
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Data/ObjectDriver.pm view on Meta::CPAN
1;
__END__
=head1 NAME
Data::ObjectDriver - Simple, transparent data interface, with caching
=head1 SYNOPSIS
## Set up your database driver code.
package FoodDriver;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Data/ObjectStore.pm view on Meta::CPAN
package Data::ObjectStore::Array;
##################################################################################
# This module is used transparently by ObjectStore to link arrays into its graph #
# structure. This is not meant to be called explicitly or modified. #
##################################################################################
use strict;
use warnings;
lib/Data/ObjectStore.pm view on Meta::CPAN
# --------------------------------------------------------------------------------
package Data::ObjectStore::Hash;
##################################################################################
# This module is used transparently by ObjectStore to link hashes into its #
# graph structure. This is not meant to be called explicitly or modified. #
##################################################################################
use strict;
use warnings;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Data/Partial/Google.pm view on Meta::CPAN
foo/bar/baz
will return the 'baz' property of the 'bar' property of the 'foo' property.
Arrays are handled transparently: if 'foo' is an array, then the rule
'bar/baz' will be applied to every entry in 'foo'.
=head2 Sub-selection
Use the parentheses to select specific properties from inside another:
view all matches for this distribution