Free template system software for linux

Template::Ast is a Perl module to process ASTs for Perl Template Toolkit.

SYNOPSIS

use Template::Ast;

# Rebuild AST stored in file:
$ast = Template::Ast->read(foo.ast) or
die Template::Ast->error();

# Writing existing AST to file:
$ast = { Marry => [24, F], John => [21, M] };
Template::Ast->write($ast, foo.ast) or
die Template::Ast->error();

$ast = Template::Ast->merge([1,2,3], undef); # [1,2,3]
$ast = Template::Ast->merge(undef, [1,2,3]); # [1,2,3]
$ast = Template::Ast->merge(undef, undef); # undef

$ast = Template::Ast->merge({A=>1,B=>2}, [C]); # [C]
$ast = Template::Ast->merge([1,2,3], [5,6]); # [5,6]
$ast = Template::Ast->merge([{A=>1},2], 5); # 5

$ast = Template::Ast->merge({A=>1,B=>2}, {C=>3}); # {A=>1,B=>2,C=>3}
$ast = Template::Ast->merge({A=>1,B=>2}, {B=>3}); # {A=>1,B=>3}

# {A=>1,B=>2}
$ast = Template::Ast->merge({A=>1,B=>undef}, {A=>undef,B=>2});

Template::Ast->merge(
{A=>1,B=>{C=>1,D=>2}},
{B=>{C=>1,D=>3,E=>4}}
); # {A=>1,B=>{C=>1,D=>3,E=>4}}

Template::Ast->merge(
{A=>1,B=>{C=>[1,2]}},
{B=>{C=>[3,4]}}
); # {A=>1,B=>{C=>[3,4]}}

print Template::Ast->dump([$vars], [vars]);

ASTs are essential in the programming model based on Perl Template Toolkit. This module provides some easy interface to do the dirty work involved in AST handling. The term AST used here are referred to any Perl referece pointed to a complex data structure, such as a nested hash, a nested array, or such.

HTML::Template module attempts to make using HTML templates simple and natural.
HTML::Template library extends standard HTML with a few new tags for variables, loops, if/else blocks and includes.
A file written with HTML and these new tags is called a template. Using this module you fill in the values for the variables and loops declared in the template.
This allows you to seperate design (the HTML) from the data, which you generate in the Perl script. While there are many other HTML template systems available, this module is simple and fast.
It doesnt try to reinvent Perl CGI, it just augments HTML with a few new and very useful abilities.
Enhancements:
- A new option was added to enforce Taint mode for unescaped variables.
- Several long-standing bugs were fixed.
- The enhanced tests produced by the Phalanx project are now part of the module.

HCKit::Template is a Perl module with a template system for HTML construction.

This module constructs an HTML page from a template. The conversion proceeds with the help of rewrite rules and data sources. Rewrite rules can be specified in the template file itself, or in the Perl script. Data sources can be XML files, or dynamically constructed in the Perl script.

Template::Magic is a Perl module for magic merger of runtime values with templates.

SYNOPSIS

Just add these 2 magic lines to your code...

use Template::Magic;
Template::Magic->new->print( /path/to/template );

to have all your variable and subroutines merged with the template file, or set one or more constructor array to customize the output generation as you need:

use Template::Magic qw( -compile );

$tm = new Template::Magic
paths => [ qw(/any/path /any/other/path) ] ,
markers => [ qw( < / > ) ] ,
lookups => [ %my_hash, $my_obj, main ] ,
zone_handlers => [ &my_zone_handler, _EVAL_ ] ,
value_handlers => [ DEFAULT, &my_value_handler ] ,
text_handlers => sub {print lc $_[1]} ,
output_handlers => sub {print uc $_[1]} ,
post_handlers => &my_post_handler ,
options => no_cache ;

$tm->nprint( template => /path/to/template
lookups => %my_special_hash );

gdWebSuite System is a script that is designed to be a full featured system for user registration, login, and administration on a Web site.
It also supports account activation and retrieving lost passwords. gdWebSuite System supports visual templates and different styles for each template.
Enhancements:
- New administration features for uploading avatars, a new avatar selection, and one new admin style were added.
- A private message system was started.
- Some changes and updates were made to various parts of the code.

HTML::Template::Set is a HTML::Template extension that adds set support.

SYNOPSIS

in your HTML:

< TMPL_SET NAME="handler" >apples_to_oranges< /TMPL_SET >
< TMPL_SET NAME="title" >Apples Are Green< /TMPL_SET >
< HTML >
< HEAD >
< TITLE >< TMPL_VAR NAME="title" >< /TITLE >
< /HEAD >

< BODY >
< H1 >< TMPL_VAR NAME="title" >< /H1 >
< HR >
< BR >
< B >You authenticated as: < /B > < TMPL_VAR NAME="ENV_REMOTE_USER" >< BR >< BR >
< TMPL_IF NAME="oranges" >You prefer oranges< /TMPL_IF >
< /BODY >
< /HTML >

in your script:

use HTML::Template::Set;

my $tmpl = new HTML::Template::Set(
filename => foo.tmpl,
associate_env => 1
);

my $handler = $tmpl->param(handler);
if ($handler and $handler eq apples_to_oranges) {
$tmpl->param(oranges => 1);
}

print $tmpl->output();

The MfGames.Template library is a C# native library for creating template libaries.

MfGames.Template was inspired by NVelocity, but was designed from the ground up to use the CIL internals, such as System.CodeDom and internal compliation to handle the template language.

Because of this, it supports C# code as the template "language". In addition, compiled templates are actually compiled down into bytecode, using the built-in compiler.

Template::Parser::CET is a Template::Alloy based parser for the TT2 engine.

SYNOPSIS

use Template;
use Template::Parser::CET;

my $t = Template->new(
PARSER => Template::Parser::CET->new
);


# you can override all instances of TT
# by any of the following methods
use Template::Parser::CET activate => 1;

# OR
use Template::Parser::CET;
Template::Parser::CET->activate;

# OR
use Template::Config;
$Template::Config::PARSER = Template::Parser::CET;

my $t = Template->new;

Template::Parser::CET provides much or most of the TT3 syntax and runs on the current TT2 engine.

Template::Alloy which was formerly known as CGI::Ex::Template (CET) provides a fast implementation of TT2 and TT3. There are some cases where Template::Toolkit is faster. There are also some cases where shops have custom providers, or custom stashes that require the use of the current TT2 engine. In these cases, Template::Parser::CET provides the best of both worlds - offering TT2 AND TT3 syntax and running on the existing platform making use of all of your current work (In many cases CET should be able to do this anyway).

This module may eventually be made obsolete when the final real Template::Toolkit 3 engine by Andy Wardley is released. But that would only be a good thing. If the TT3 engine doesnt provide full backward compatibility this module will.

CET has provided TT3 features since Spring of 2006 but there has been little reported uptake. The TT3 features/extended syntax are very compelling. For various reasons people chose not to use CET. Now people can use TT2 and get the features of TT3 (through CET) today.

Hopefully Template::Parser::CET and Template::Alloy can be used in the same spirit as Pugs is used for Perl 6. All of the code from CET and Template::Parser::CET are free for use in TT3.