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.

XMLNews::HTMLTemplate is Perl module for converting NITF to HTML.

SYNOPSIS

use XMLNews::HTMLTemplate;

my $template = new XMLNews::HTMLTemplate();
$template->readTemplate("mytemplate.html");

$template->applyTemplate("output.html", "story.xml", "story.rdf");

NOTE: this module requires the XML::Parser and XMLNews::Meta modules.

WARNING: this module is not thread-safe or re-entrant.

The XMLNews::HTMLTemplate module provides a simple mechanism for creating HTML pages from XML/NITF news stories and/or XML/RDF metadata files based on a user-supplied template file. The template is a simple HTML file (SGML or XML flavour) using special template commands, which the user includes as processing instructions, as in the following example:

To create an HTML page, you must first create an empty HTMLTemplate object:

my $template = new XMLNews::HTMLTemplate();

Next, you load the HTML template into the object:

$template->readTemplate("mytemplate.html");

Now, you can apply the same compiled template object repeatedly to different XML/NITF and/or XML/RDF documents to generate HTML pages:

$template->applyTemplate("outfile.html", "newsstory.xml", "newsstory.rdf");

Blitz templates is a fast template engine written in C and compiled as a PHP module. It started as a php_templates replacement, but developed into much more.
The project is based on extensible template controllers (custom view classes in PHP) and weakly-active templates (simple logic in HTML).
Enhancements:
- Lot of code cleanup was done.
- The "parse" and "include" methods were improved, and their "vars" argument is not a globals array anymore; now its just an arbitrary iteration set and both methods comply with set/block/fetch.
- Templates included by the "include" method from PHP code inherit globals from the caller automatically.
- Corresponding tests were updated.
- A new article was added to the documentation: "Quick Geek Blitz Tutorial", which is addressed to those professionals who want to learn API basics in a minimum of time.

HTML::Template::JIT is a just-in-time compiler for HTML::Template. Templates are compiled into native machine code using Inline::C.
When using HTML::Template::JIT, the compiled code is stored to disk and reused on subsequent calls. HTML::Template::JIT is up to 8 times as fast as HTML::Template using caching.
Enhancements:
- Fixed param() to allow for blessed hash-refs. [Alex Kapranoff]
- Fixed url-escaping to work with UTF-8 characters. [Alex Kapranoff]
- Added support for JS escaping. [Alex Kapranoff]
- Fixed a compatibility problem with HTML::Template v2.8, which is now a prerequisite.

kmail templates is a patch for current 3.5 branch of kdepim package which replaces Phrases configuration with more rich templates engine.

Templates use template syntax of well-known Thebat! mail client and allow construct a little more complicated messages than now.

Smarty project is a template engine for PHP. Many other template engines for PHP provide basic variable substitution and dynamic block functionality.
Smarty takes a step further to be a "smart" template engine, adding features such as configuration files, template functions, and variable modifiers, and making all of this functionality as easy as possible to use for both programmers and template designers.
Smarty also converts the templates into PHP scripts, eliminating the need to parse the templates on every invocation. This makes Smarty extremely scalable and managable for large application needs.
Main features:
- Caching: Smarty provides fine-grained caching features for caching all or parts of a rendered web page, or leaving parts uncached. Programmers can register template functions as cacheable or non-cachable, group cached pages into logical units for easier management, etc.
- Configuration Files: Smarty can assign variables pulled from configuration files. Template designers can maintain values common to several templates in one location without intervention from the programmer, and config variables can easily be shared between the programming and presentation portions of the application.
- Security: Templates do not contain PHP code. Therefore, a template designer is not unleashed with the full power of PHP, but only the subset of functionality made available to them from the programmer (application code.)
- Easy to Use and Maintain: Web page designers are not dealing with PHP code syntax, but instead an easy-to-use templating syntax not much different than plain HTML. The templates are a very close representation of the final output, dramatically shortening the design cycle.
- Variable Modifiers: The content of assigned variables can easily be adjusted at display-time with modifiers, such as displaying in all upper-case, html-escaped, formatting dates, truncating text blocks, adding spaces between characters, etc. Again, this is accomplished with no intervention from the programmer.
- Template Functions: Many functions are available to the template designer to handle tasks such as generating HTML code segments (dropdowns, tables, pop-ups, etc.), displaying content from other templates in-line, looping over arrays of content, formatting text for e-mail output, cycling though colors, etc.
- Filters: The programmer has complete control of template output and compiled template content with pre-filters, post-filters and output-filters.
- Resources: Templates can be pulled from any number of sources by creating new resource handlers, then using them in the templates.
- Plugins: Almost every aspect of Smarty is controlled through the use of plugins. They are generally as easy as dropping them into the plugin directory and then mentioning them in the template or using them in the application code. Many user-community contributions are also available. (See the plugins section of the forum and wiki.)
- Add-ons: Many user-community contributed Add-ons are available such as Pagination, Form Validation, Drop Down Menus, Calander Date Pickers, etc. These tools help speed up the development cycle, there is no need to re-invent the wheel or debug code that is already stable and ready for deployment. (see the Add-ons section of the forum and wiki.)
- Debugging: Smarty comes with a built-in debugging console so the template designer can see all of the assigned variables and the programmer can investigate template rendering speeds.
- Compiling: Smarty compiles templates into PHP code behind the scenes, eliminating run-time parsing of templates.
- Performance: Smarty performs extremely well, despite its vast feature set. Most of Smartys capabilities lie in plugins that are loaded on-demand. Smarty comes with numerous presentation tools, minimizing your application code and resulting in quicker, less error-prone application development/deployment. Smarty templates get compiled to PHP files internally (once), eliminating costly template file scans and leveraging the speed of PHP op-code accelerators.

HTML::Template::Extension::DOC are plugins for comments in template.

SYNOPSIS

use HTML::Template::Extension;

my $text = qq
|
< HTML >< HEAD >< /HEAD >< BODY >
< H1 >This is a template example...< /H1 >
< TMPL_DOC >An example use of TMPL_DOC tag < /TMPL_DOC >
The sum between 1+1 is: < TMPL_VAR NAME="result" >
< /BODY >< /HTML >
|;

my $comp = new HTML::Template::Extension(
scalarref => $text,
plugins=>["DOC"],
);

$comp->param(result => 1+1);

print $comp->output;

# OUTPUT:
#
# < HTML >< HEAD >< /HEAD >< BODY >
# < H1 >This is a template example...< /H1 >
# The sum between 1+1 is: 2
# < /BODY >< /HTML >

DOC plugin add a < TMPL_DOC >some comments< /TMPL_DOC > to standard HTML::Template syntax to permit to add comments to template that, for indeed, a web graphic designer can view in a WYSIWYG environment.

All text between < TMPL_DOC > and < /TMPL_DOC > and tag itself will be deleted before HTML::Template parsing and retuning template output.