NAME
HTML::CTPP2 - Perl interface for CTPP2 librarySYNOPSIS
First you should make template, file `hello.tmpl`:
Foo: <TMPL_var foo>
<TMPL_if array>
Here is loop body:
<TMPL_loop array>
Key: <TMPL_var key>
</TMPL_loop>
</TMPL_if>
Now create PERL script:
#!/usr/bin/perl -w
use strict;
use HTML::CTPP2;
my $T = new HTML::CTPP2();
# Parse template
my $Bytecode = $T -> parse_template("hello.tmpl");
# Fill parameters
my %H = ("foo" => "bar", array => [ { "key" => "first" }, { "key" => "second"} ]);
$T -> param(\%H);
my $Result = $T -> output($Bytecode);
Now check output:
Foo: bar
Here is loop body:
Key: first
Key: second
Since version 2.1.1 of CTPP *library*, you can also use expressions in <TMPL_if
and in <TMPL_var operators:
File `math_expr.tmpl`:
<TMPL_var a> + <TMPL_var b> = <TMPL_var (a + b)>
<TMPL_if (age < 18 && age > 90)>Invalid age<TMPL_else>Age correct</TMPL_if> DESCRIPTION
This module is very similar to well-known Sam Tregar's HTML::Template but works
in 22 - 25 times faster and contains extra functionality.
CTPP2 template language dialect contains 9 operators: <TMPL_var>, <TMPL_if>,
<TMPL_elsif>, <TMPL_else>, <TMPL_unless>, <TMPL_loop>, <TMPL_udf>, <TMPL_include>
and <TMPL_comment>.THE TAGS
In order to simplify the make-up, all operators names are case insensitive,
that is why the notifications such as: <TMPL_var , <TmPl_VaR , <tmpl_VAR
are equal.
BUT the names of variables are case sensitive, that's why for example:
<TMPL_var ABC>, <TMPL_var abc>, <TMPL_var Abc> are not in equal state.
Parameters, which names starting with a symbol of underlining
(for example __FIRST__) are reserved names and should NOT be used
by the developer. Variable names can be composed of letters, numbers,
and underscores (_). Every variable name in CTPP must start with a letter.
You can access subproperties (hash references to oher object) of variable by
specifying it after variable name separated by dot '.': <TMPL_var foo.bar>.TMPL_var
<TMPL_var VAR_NAME>, <TMPL_udf VAR_NAME> - Direct parameter output.
In CTPP template engine two types of variables are defined: local and global.
The sense of these two concepts is completely equal with a similar idea
in the other algorithmic languages such as C++ & Perl.
For variable output use operator <TMPL_var VAR_NAME>
Example 1.1
Template: "Hello, <b><TMPL_var username></b>!"
Parameter: username => "Olga"
Output: "Hello, Olga!"
You can use user defined functions to make a variable output.
Example 1.2
Template: "<a href="/index.cgi?username=<TMPL_var URLESCAPE(username)>">"
Parameter: username => "Àíäðåé" (string in non-ascii7 character set)
Output: "<a href="/index.cgi?username=%C0%ED%E4%F0%E5%E9">"
Example 1.3
Template: User <TMPL_var user.name> has id <TMPL_var user.id>
Parameter: user => { name => "Fred", id => 1234 }
Output: User Fred has id 1234TMPL_if, TMPL_unless
These operators impose condition on your template output, it depends on the
result of logical expression placed to the right of the operator's body.
CTPP defines four operators of condition: <TMPL_if LOGICAL_EXPR>,
<TMPL_elsif LOGICAL_EXPR>, <TMPL_else> and <TMPL_unless LOGICAL_EXPR>.
Operators evaluates logical expression to the result and according to it
executes or not the further instructions. You can also use variables
(local and global) and user defined functions inside of the operator's body.
Example 2.1
<TMPL_if LOGICAL_EXPR>
Some instructions if result has true value.
<TMPL_elsif OTHER_EXPRESSION>
Some instructions if result has false value.
<TMPL_else>
Else-branch/
</TMPL_if>
<TMPL_unless LOGICAL_EXPR1>
Some instructions if result has false value.
<TMPL_elsif LOGICAL_EXPR2>
Some instructions if evaluation result of
LOGICAL_EXPR2 has true value.
<TMPL_else>
Some instructions if result has true value.
</TMPL_unless>
The branches of <TMPL_elsif> and <TMPL_else> are not firmly binds,
it means that the following notification is allowed:
<TMPL_if LOGICAL_EXPR> Some instructions </TMPL_if>.
Thus the operator <TMPL_unless differs from the operator <TMPL_if in the
executing some instructions if the evaluated value is false.TMPL_loop
The loop - The multiple repeating of some pre-defined actions.
The only type of loops has been defined in CTPP - the forward running over
through the data array. The operator corresponding with this action looks
like the following:
<TMPL_loop MODIFIERS LOOP_NAME>
The LOOP instructions.
</TMPL_loop>
If you evidently put the mark to use context variables in the loop body,
CTPP inserts seven special variables, called context vars. The names of these
variables start with the double underline, this fact points to their system
meaning. Set of values for "context vars":
* __FIRST__ - sets to "1" during the first loop iteration,
in other cases not defined.
* __LAST__ - sets to the last iteration number,
otherwise is not defined.
* __INNER__ - accommodates the number from the second to the pre-last
iteration, otherwise undefined
* __ODD__ - the number of an odd iteration. For the even one - undefined.
* __COUNTER__ - the number of current iteration.
* __EVEN__ - opposite to the __ODD__ variable.
* __SIZE__ - the whole number of the loop iterations.
* __CONTENT__ - contains value of current iterationTMPL_include
In some cases it happens to allocate conveniently identical parts in several
templates (for example, heading or the menu on page) and to place them in one file.
This is done by operator <TMPL_include filename.tmpl>.
Example 3.1:
File `main.tmpl`:
<TMPL_loop foo>
<TMPL_include "filename.tmpl" map(bar : baz, orig_param : include_param)>
</TMPL_loop>
File filename.tmpl:
<TMPL_var baz>
You can rename variable in included templates. In example 3.1 variable 'baz'
in file 'filename.tmpl' was renamed to 'bar' and 'orig_param' to 'include_param'.
This is useful when you include one template many times in main template.
Attention! You CAN NOT place a part of a loop or condition in separate templates.
In other words, this construction will not work:
Example 3.2
File `main.tmpl`:
<TMPL_if foo>
<TMPL_include 'abc.tmpl'>
File `abc.tmpl`:
</TMPL_if>TMPL_comment
All characters between <TMPL_comment> and </TMPL_comment> are ignored. This is
useful to comment some parts of template.Built-in functions
There are a variety of situations when you need to represent data according
to some condition. To simplify the solution of this problem CTPP support
Built-in Functions. ou can call them from the bodies of <TMPL_if, <TMPL_unless,
<TMPL_var and <TMPL_udf operators. The following example shows how to call
Built-in function:
<TMPL_var HTMLESCAPE(name)>
<TMPL_if IN_SET(name, 1, 2, 3)>
Variable "name" is set to "1", "2" or "3".
</TMPL_if>
CTPP2 support following built-in functions:
* URLESCAPE
* HTMLESCAPE
* XMLESCAPE
* NUM_FORMAT
* GETTEXT (_)
* IN_SET
* HREF_PARAM
* FORM_PARAM
* DATE_FORMAT
* BASE64_ENCODE
* BASE64_DECODE
* MD5
* ICONV
* VERSION
* OBJ_DUMP
* CAST
Please refer to CTPP2 library documentation to get detailed
information about these functions.METHODS
HTML::CTPP2() - constructor
Call new() to create a new HTML::CTPP2 object:
my $T = new HTML::CTPP2();
You can also change some internal variables of CTPP engine:
my $T = new HTML::CTPP2(arg_stack_size => 1024,
code_stack_size => 1024,
steps_limit => 10240,
max_functions => 1024);
'arg_stack_size' - Max. size of stack of arguments
'code_stack_size' - Max. stack size
'max_functions' - Max. number of functions in CTPP standard library
Normally you should now change these parameters, to explanation please
refer to CTPP library documentation.
'steps_limit' - template execution limit (in steps). Default value
is 1 048 576 (1024*1024). You can limit template execution time by
specifying this parameter.
Note, if execution limit is reached, template engine generates error
and you should use eval {} to catch it. param() - set some parameters
my %Hash = ("foo" => "bar", "blahblah" => "clah-clah");
$T -> param(\%H);clear_params(), reset() - reset all the parameters to undef.
$T -> clear_params();
or
$T -> reset();output() - returns output as string
In most situations you can print this directly to standard output:
print $T -> output($bytecode);include_dirs() - set list of include directories
my @IncludeDirs = ("/home/www/tmpl", "/usr/share/www/common_templates");
$T -> include_dirs(\@IncludeDirs);
CTPP parser will search templates in specified directories.parse_template() - compile source code of template to CTPP bytecode
my $bytecode = $T -> parse_template("hello.tmpl");load_bytecode() - load precompiled template from specified file
my $bytecode = $T -> load_bytecode("hello.ct2");
ATTENTION: you should specify FULL path to precompiled file,
CTPP DOES NOT uses include_dirs to search bytecode!dump_params() - get internal representation of all given parameters.
print $T -> dump_params();save() - save compiled bytecode to file
Since you have compiled template to bytecode you may store it in file.
This increases speed of loading template.
# Parse template
my $bytecode = $T -> parse_template("hello.tmpl");
# Save bytecode to binary file
$bytecode -> save("hello.ct2");
# Now we can load compiled template without parsing original file
my $other_bytecode = $T -> load_bytecode("hello.ct2");load_udf() - load user-defined function from external storage
If you have a shared library wich contains compiled user-defined functions,
you may load it by calling method load_udf().
Please refer to documentation to explain, how you can write user-defined CTPP
functions in C++.
$T -> load_udf('/shared/library/name.so', 'UserDefinedFunctionName');AUTHOR
Andrei V. Shetuhin (reki@reki.ru)
SEE ALSO
perl(1), HTML::Template(3), HTML::Template::Pro(3)
WEBSITE
http://ctpp.havoc.ru/
LICENSE
Copyright (c) 2006 - 2008 CTPP Team
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
4. Neither the name of the CTPP Team nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.1 POD Error
The following errors were encountered while parsing the POD:
- Around line 117:
Non-ASCII character seen before =encoding in '"Àíäðåé"'. Assuming CP1252