| Name : perl-Template-Alloy
| |
| Version : 1.020
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : 1.1
| Date : 2018-12-03 21:58:29
|
| Group : Development/Libraries/Perl
| Source RPM : perl-Template-Alloy-1.020-1.1.src.rpm
|
| Size : 0.58 MB
| |
| Packager : (none)
| |
| Summary : TT2/3, HT, HTE, Tmpl, and Velocity Engine
|
Description :
\"An alloy is a homogeneous mixture of two or more elements\"
(http://en.wikipedia.org/wiki/Alloy).
Template::Alloy represents the mixing of features and capabilities from all
of the major mini-language based template systems (support for
non-mini-language based systems will happen eventually). With
Template::Alloy you can use your favorite template interface and syntax and
get features from each of the other major template systems. And
Template::Alloy is fast - whether your using mod_perl, CGI, or running from
the commandline. There is even Template::Alloy::JS for getting a little
more speed when that is necessary.
Template::Alloy happened by accident (accidentally on purpose). The
Template::Alloy (Alloy hereafter) was originally a part of the CGI::Ex
suite that performed simple variable interpolation. It used TT2 style
variables in TT2 style tags \"[% foo.bar %]\". That was all the original
Template::Alloy did. This was fine and dandy for a couple of years. In
winter of 2005-2006 Alloy was revamped to add a few features. One thing led
to another and soon Alloy provided for most of the features of TT2 as well
as some from TT3. Template::Alloy now provides a full-featured
implementation of the Template::Toolkit language.
After a move to a new company that was using HTML::Template::Expr and
Text::Tmpl templates, support was investigated and interfaces for
HTML::Template, HTML::Template::Expr, Text::Tmpl, and Velocity (VTL) were
added. All of the various engines offer the same features - each using a
different syntax and interface.
More recently, the Template::Alloy::JS capabilities were introduced to
bring Javascript templates to the server side (along with an increase in
speed if ran in persistent environments).
Template::Toolkit brought the most to the table. HTML::Template brought the
LOOP directive. HTML::Template::Expr brought more vmethods and using
vmethods as top level functions. Text::Tmpl brought the COMMENT directive
and encouraged speed matching (Text::Tmpl is almost entirely C based and is
very fast). The Velocity engine brought AUTO_EVAL and
SHOW_UNDEFINED_INTERP.
Most of the standard Template::Toolkit documentation covering directives,
variables, configuration, plugins, filters, syntax, and vmethods should
apply to Alloy just fine (This pod tries to explain everything - but there
is too much). See the Template::Alloy::TT manpage for a listing of the
differences between Alloy and TT.
Most of the standard HTML::Template and HTML::Template::Expr documentation
covering methods, variables, expressions, and syntax will apply to Alloy
just fine as well.
Most of the standard Text::Tmpl documentation applies, as does the
documentation covering Velocity (VTL).
So should you use Template::Alloy ? Well, try it out. It may give you no
visible improvement. Or it could.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl/SLE_12_SP4/noarch |
Hmm ... It's impossible ;-) This RPM doesn't exist on any FTP server
Provides :
perl(Template::Alloy)
perl(Template::Alloy::Compile)
perl(Template::Alloy::Context)
perl(Template::Alloy::EvalPerlHandle)
perl(Template::Alloy::Exception)
perl(Template::Alloy::HTE)
perl(Template::Alloy::Iterator)
perl(Template::Alloy::Operator)
perl(Template::Alloy::Parse)
perl(Template::Alloy::Perl)
perl(Template::Alloy::Play)
perl(Template::Alloy::Stream)
perl(Template::Alloy::TT)
perl(Template::Alloy::Tmpl)
perl(Template::Alloy::VMethod)
perl(Template::Alloy::Velocity)
perl(Template::Alloy::_ContextStash)
perl-Template-Alloy
Requires :
