X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=lib%2FMaypole%2FView%2FTT.pm;h=c79c027633f23ae55623b10eda75cd0c1dbb32ca;hb=628ecd5d9d294e601c79c7509140d02dcd7a1d40;hp=21e2485b794a7d3a3fe6f5b694b4aa58a7b1de14;hpb=ef3da5818c452a331e863d30efc41f5b65d0f624;p=maypole.git diff --git a/lib/Maypole/View/TT.pm b/lib/Maypole/View/TT.pm index 21e2485..c79c027 100644 --- a/lib/Maypole/View/TT.pm +++ b/lib/Maypole/View/TT.pm @@ -2,17 +2,32 @@ package Maypole::View::TT; use base 'Maypole::View::Base'; use Maypole::Constants; use Template; +use File::Spec::Functions qw(catdir tmpdir); + +use strict; +our $VERSION = "1." . sprintf "%04d", q$Rev$ =~ /: (\d+)/; sub template { my ( $self, $r ) = @_; - my $template = Template->new( { INCLUDE_PATH => [ $self->paths($r) ] } ); + + unless ($self->{tt}) { + my $view_options = $r->config->view_options || {}; + $self->{provider} = Template::Provider->new($view_options); + $self->{tt} = Template->new({ + %$view_options, + LOAD_TEMPLATES => [ $self->{provider} ], + }); + } + + $self->{provider}->include_path([ $self->paths($r) ]); + my $output; - if ( $template->process( $r->template, { $self->vars($r) }, \$output ) ) { + if ($self->{tt}->process( $r->template, { $self->vars($r) }, \$output )) { $r->{output} = $output; return OK; } else { - $r->{error} = $template->error; + $r->{error} = $self->{tt}->error; return ERROR; } } @@ -27,19 +42,28 @@ Maypole::View::TT - A Template Toolkit view class for Maypole BeerDB->config->view("Maypole::View::TT"); # The default anyway + # Set some Template Toolkit options + BeerDB->config->view_options( { + TRIM => 1, + COMPILE_DIR => '/var/tmp/mysite/templates', + } ); + =head1 DESCRIPTION -This is the default view class for Maypole; it uses the Template Toolkit -to fill in templates with the objects produced by Maypole's model classes. -Please see the Maypole manual, and in particular, the C chapter, -for the template variables available and for a refresher on how template -components are resolved. +This is the default view class for Maypole; it uses the Template Toolkit to +fill in templates with the objects produced by Maypole's model classes. Please +see the Maypole manual, and in particular, the L +chapter for the template variables available and for a refresher on how +template components are resolved. + +The underlying Template toolkit object is configured through +C<$r-Econfig-Eview_options>. See L for available +options. =over 4 =item template - Processes the template and sets the output. See L =back