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 my $view_options = $r->config->view_options || {};
14 $self->{provider} ||= Template::Provider->new();
15 $self->{tt} ||= Template->new({
16 COMPILE_DIR => catdir(tmpdir(), $r->config->application_name),
18 LOAD_TEMPLATES => [ $self->{provider} ],
21 $self->{provider}->include_path([ $self->paths($r) ]);
24 if ($self->{tt}->process( $r->template, { $self->vars($r) }, \$output )) {
25 $r->{output} = $output;
29 $r->{error} = $self->{tt}->error;
38 Maypole::View::TT - A Template Toolkit view class for Maypole
42 BeerDB->config->view("Maypole::View::TT"); # The default anyway
44 # Set some Template Toolkit options
45 BeerDB->config->view_options( {
47 COMPILE_DIR => '/var/tmp/mysite/templates',
52 This is the default view class for Maypole; it uses the Template Toolkit
53 to fill in templates with the objects produced by Maypole's model classes.
54 Please see the Maypole manual, and in particular, the C<View> chapter,
55 for the template variables available and for a refresher on how template
56 components are resolved.
58 The underlying Template toolkit object is configured through
59 C<$r-E<gt>config-E<gt>view_options>. See L<Template> for available options.
65 Processes the template and sets the output. See L<Maypole::View::Base>