1 package Maypole::View::TT;
2 use base 'Maypole::View::Base';
3 use Maypole::Constants;
5 use File::Spec::Functions qw(catdir tmpdir);
8 our $VERSION = "1." . sprintf "%04d", q$Rev$ =~ /: (\d+)/;
11 my ( $self, $r ) = @_;
13 unless ($self->{tt}) {
14 my $view_options = $r->config->view_options || {};
15 $self->{provider} = Template::Provider->new($view_options);
16 $self->{tt} = Template->new({
18 LOAD_TEMPLATES => [ $self->{provider} ],
22 $self->{provider}->include_path([ $self->paths($r) ]);
25 if ($self->{tt}->process( $r->template, { $self->vars($r) }, \$output )) {
26 $r->{output} = $output;
30 $r->{error} = $self->{tt}->error;
39 Maypole::View::TT - A Template Toolkit view class for Maypole
43 BeerDB->config->view("Maypole::View::TT"); # The default anyway
45 # Set some Template Toolkit options
46 BeerDB->config->view_options( {
48 COMPILE_DIR => '/var/tmp/mysite/templates',
53 This is the default view class for Maypole; it uses the Template Toolkit to
54 fill in templates with the objects produced by Maypole's model classes. Please
55 see the L<Maypole manual|Maypole::Manual>, and in particular, the
56 L<view|Maypole::Manual::View> chapter for the template variables available and
57 for a refresher on how template components are resolved.
59 The underlying Template toolkit object is configured through
60 C<$r-E<gt>config-E<gt>view_options>. See L<Template|Template> for available
67 Processes the template and sets the output. See L<Maypole::View::Base>