CGI::Application::Plugin::AnyTemplate 0.18

CGI::Application::Plugin::AnyTemplate allows you to use any supported Perl templating system using a single consistent interface.<br /><br />Currently supported templating systems include HTML::Template, HTML::Template::Expr, HTML::Template::Pluggable, Template::Toolkit and Petal.<br /><br />You can access any of these templating systems using the same interface. In this way, you can use the same code and switch templating systems on the fly.<br /><br />This approach has many uses. For instance, it can be useful in migrating your application from one templating system to another.<br />Embedded Components<br /><br />In addition to template abstraction, AnyTemplate also provides a embedded component mechanism. For instance, you might include a header component at the top of every page and a footer component at the bottom of every page.<br /><br />These components are actually full CGI::Application run modes, and can do anything normal run mode can do, including processing form parameters and filling in their own templates. See below under "EMBEDDED COMPONENTS" for details.<br />Multiple Named Template Configurations<br /><br />You can set up multiple named template configurations and select between them at run time.<br /><br /> sub cgiapp_init {<br /> my $self = shift;<br /><br /> # Can't use Template::Toolkit any more -<br /> # The boss wants everything has to be XML,<br /> # so we switch to Petal<br /><br /> # Set old-style template options (legacy scripts)<br /> $self->template('oldstyle')->config(<br /> default_type => 'TemplateToolkit',<br /> TemplateToolkit => {<br /> POST_CHOMP => 1,<br /> }<br /> );<br /> # Set new-style template options as default<br /> $self->template->config(<br /> default_type => 'Petal',<br /> auto_add_template_extension => 0,<br /> );<br /> }<br /><br /> sub old_style_runmode {<br /> my $self = shift;<br /><br /> # ...<br /><br /> # use TemplateToolkit to fill template edit_user.tmpl<br /> $self->template('oldstyle')->fill('edit_user', %params);<br /><br /> }<br /><br /> sub new_style_runmode {<br /> my $self = shift;<br /><br /> # ...<br /><br /> # use Petal to fill template edit_user.xhml<br /> $self->template->fill('edit_user.xhtml', %params);<br /><br /> }<br /><br />Flexible Syntax<br /><br />The syntax is pretty flexible. Pick a style that's most comfortable for you.<br />CGI::Application::Plugin::TT style syntax<br /><br /> $self->template->process('edit_user', %params);<br /><br />or (with slightly less typing):<br /><br /> $self->template->fill('edit_user', %params);<br /><br />CGI::Application load_tmpl style syntax<br /><br /> my $template = $self->template->load('edit_user');<br /> $template->param('foo' => 'bar');<br /> $template->output;<br /><br />Verbose syntax (for complete control)<br /><br /> my $template = $self->template('named_config')->load(<br /> file => 'edit_user'<br /> type => 'TemplateToolkit'<br /> add_include_paths => '.',<br /> );<br /><br /> $template->param('foo' => 'bar');<br /> $template->output;<br /><br />See also below under "CHANGING THE NAME OF THE 'template' METHOD".

Requirements:	No special requirements
Platforms:	*nix, Linux
Keyword:	Component,  Default Type,  Instance,  Options,  Params,  Petal,  Shift,  Style,  Supported,  Syntax,  System,  Systems,  Template,  Templategtparam Foo,  Templatetoolkit,  Templating
Users rating:	0/10