X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=lib%2FMaypole%2FView%2FTT.pm;h=40fa5651dcc9480db76f856e5f1a0a40e8aeb44b;hb=8617321ebf13ce6b63d41a65a003d153f2b5cc5e;hp=9142f3ebe51bdbda78ffbde8f2a37e5de11f9f50;hpb=5ba93a09518403ae28e8a71b5299e2458a6dfa0b;p=maypole.git diff --git a/lib/Maypole/View/TT.pm b/lib/Maypole/View/TT.pm index 9142f3e..40fa565 100644 --- a/lib/Maypole/View/TT.pm +++ b/lib/Maypole/View/TT.pm @@ -2,17 +2,38 @@ 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 || {}; + (my $driver_name = ref $r) =~ s/::/_/g; + my $compile_dir = catdir(tmpdir(), $driver_name); + $self->{provider} = Template::Provider->new( + COMPILE_DIR => $compile_dir, + %$view_options, + ); + $self->{tt} = Template->new({ + COMPILE_DIR => $compile_dir, + %$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; } } @@ -25,7 +46,13 @@ Maypole::View::TT - A Template Toolkit view class for Maypole =head1 SYNOPSIS - BeerDB->config->{view} = "Maypole::View::TT"; # The default anyway + 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 @@ -35,6 +62,18 @@ 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. +The underlying Template toolkit object is configured through +C<$r-Econfig-Eview_options>. See L