1 package Catalyst::View::TT;
6 use base qw/Catalyst::View/;
12 our $VERSION = '0.30';
14 __PACKAGE__->mk_accessors('template');
15 __PACKAGE__->mk_accessors('include_path');
17 *paths = \&include_path;
21 Catalyst::View::TT - Template View Class
25 # use the helper to create your View
26 myapp_create.pl view TT TT
28 # configure in lib/MyApp.pm (Could be set from configfile instead)
32 root => MyApp->path_to('root'),
34 # any TT configurations items go here
36 MyApp->path_to( 'root', 'src' ),
37 MyApp->path_to( 'root', 'lib' ),
39 TEMPLATE_EXTENSION => '.tt',
43 PRE_PROCESS => 'config/main',
44 WRAPPER => 'site/wrapper',
48 # render view from lib/MyApp.pm or lib/MyApp::Controller::SomeController.pm
50 sub message : Global {
51 my ( $self, $c ) = @_;
52 $c->stash->{template} = 'message.tt2';
53 $c->stash->{message} = 'Hello World!';
54 $c->forward('MyApp::View::TT');
57 # access variables from template
59 The message is: [% message %].
61 # example when CATALYST_VAR is set to 'Catalyst'
62 Context is [% Catalyst %]
63 The base is [% Catalyst.req.base %]
64 The name is [% Catalyst.config.name %]
66 # example when CATALYST_VAR isn't set
68 The base is [% base %]
69 The name is [% name %]
74 my ( $paths, $dlim ) = shift;
75 return () if ( !$paths );
76 return @{$paths} if ( ref $paths eq 'ARRAY' );
78 # tweak delim to ignore C:/
79 unless ( defined $dlim ) {
80 $dlim = ( $^O eq 'MSWin32' ) ? ':(?!\\/)' : ':';
82 return split( /$dlim/, $paths );
86 my ( $class, $c, $arguments ) = @_;
89 TEMPLATE_EXTENSION => '',
93 if ( ! (ref $config->{INCLUDE_PATH} eq 'ARRAY') ) {
94 my $delim = $config->{DELIMITER};
96 = _coerce_paths( $config->{INCLUDE_PATH}, $delim );
97 if ( !@include_path ) {
98 my $root = $c->config->{root};
99 my $base = Path::Class::dir( $root, 'base' );
100 @include_path = ( "$root", "$base" );
102 $config->{INCLUDE_PATH} = \@include_path;
105 # if we're debugging and/or the TIMER option is set, then we install
106 # Template::Timer as a custom CONTEXT object, but only if we haven't
107 # already got a custom CONTEXT defined
109 if ( $config->{TIMER} ) {
110 if ( $config->{CONTEXT} ) {
112 'Cannot use Template::Timer - a TT CONTEXT is already defined'
116 $config->{CONTEXT} = Template::Timer->new(%$config);
120 if ( $c->debug && $config->{DUMP_CONFIG} ) {
121 $c->log->debug( "TT Config: ", dump($config) );
124 my $self = $class->next::method(
128 # Set base include paths. Local'd in render if needed
129 $self->include_path($config->{INCLUDE_PATH});
131 $self->config($config);
133 # Creation of template outside of call to new so that we can pass [ $self ]
134 # as INCLUDE_PATH config item, which then gets ->paths() called to get list
135 # of include paths to search for templates.
137 # Use a weakend copy of self so we dont have loops preventing GC from working
139 Scalar::Util::weaken($copy);
140 $config->{INCLUDE_PATH} = [ sub { $copy->paths } ];
142 if ( $config->{PROVIDERS} ) {
144 if ( ref($config->{PROVIDERS}) eq 'ARRAY') {
145 foreach my $p (@{$config->{PROVIDERS}}) {
146 my $pname = $p->{name};
147 my $prov = 'Template::Provider';
148 if($pname eq '_file_')
150 $p->{args} = { %$config };
154 if($pname =~ s/^\+//) {
161 # We copy the args people want from the config
164 if ($p->{copy_config}) {
165 map { $p->{args}->{$_} = $config->{$_} }
166 grep { exists $config->{$_} }
167 @{ $p->{copy_config} };
170 eval "require $prov";
172 push @providers, "$prov"->new($p->{args});
176 $c->log->warn("Can't load $prov, ($@)");
180 delete $config->{PROVIDERS};
182 $config->{LOAD_TEMPLATES} = \@providers;
187 Template->new($config) || do {
188 my $error = Template->error();
189 $c->log->error($error);
199 my ( $self, $c ) = @_;
201 my $template = $c->stash->{template}
202 || $c->action . $self->config->{TEMPLATE_EXTENSION};
204 unless (defined $template) {
205 $c->log->debug('No template specified for rendering') if $c->debug;
209 my $output = $self->render($c, $template);
211 if (UNIVERSAL::isa($output, 'Template::Exception')) {
212 my $error = qq/Couldn't render template "$output"/;
213 $c->log->error($error);
218 unless ( $c->response->content_type ) {
219 $c->response->content_type('text/html; charset=utf-8');
222 $c->response->body($output);
228 my ($self, $c, $template, $args) = @_;
230 $c->log->debug(qq/Rendering template "$template"/) if $c->debug;
234 (ref $args eq 'HASH' ? %$args : %{ $c->stash() }),
235 $self->template_vars($c)
238 local $self->{include_path} =
239 [ @{ $vars->{additional_template_paths} }, @{ $self->{include_path} } ]
240 if ref $vars->{additional_template_paths};
242 unless ($self->template->process( $template, $vars, \$output ) ) {
243 return $self->template->error;
250 my ( $self, $c ) = @_;
252 my $cvar = $self->config->{CATALYST_VAR};
258 base => $c->req->base,
259 name => $c->config->{name}
270 This is the Catalyst view class for the L<Template Toolkit|Template>.
271 Your application should defined a view class which is a subclass of
272 this module. The easiest way to achieve this is using the
273 F<myapp_create.pl> script (where F<myapp> should be replaced with
274 whatever your application is called). This script is created as part
275 of the Catalyst setup.
277 $ script/myapp_create.pl view TT TT
279 This creates a MyApp::View::TT.pm module in the F<lib> directory (again,
280 replacing C<MyApp> with the name of your application) which looks
283 package FooBar::View::TT;
286 use base 'Catalyst::View::TT';
288 __PACKAGE__->config->{DEBUG} = 'all';
290 Now you can modify your action handlers in the main application and/or
291 controllers to forward to your view class. You might choose to do this
292 in the end() method, for example, to automatically forward all actions
293 to the TT view class.
295 # In MyApp or MyApp::Controller::SomeController
298 my( $self, $c ) = @_;
299 $c->forward('MyApp::View::TT');
304 There are a three different ways to configure your view class. The
305 first way is to call the C<config()> method in the view subclass. This
306 happens when the module is first loaded.
308 package MyApp::View::TT;
311 use base 'Catalyst::View::TT';
313 MyApp::View::TT->config({
315 MyApp->path_to( 'root', 'templates', 'lib' ),
316 MyApp->path_to( 'root', 'templates', 'src' ),
318 PRE_PROCESS => 'config/main',
319 WRAPPER => 'site/wrapper',
322 The second way is to define a C<new()> method in your view subclass.
323 This performs the configuration when the view object is created,
324 shortly after being loaded. Remember to delegate to the base class
325 C<new()> method (via C<$self-E<gt>next::method()> in the example below) after
326 performing any configuration.
332 MyApp->path_to( 'root', 'templates', 'lib' ),
333 MyApp->path_to( 'root', 'templates', 'src' ),
335 PRE_PROCESS => 'config/main',
336 WRAPPER => 'site/wrapper',
338 return $self->next::method(@_);
341 The final, and perhaps most direct way, is to define a class
342 item in your main application configuration, again by calling the
343 uniquitous C<config()> method. The items in the class hash are
344 added to those already defined by the above two methods. This happens
345 in the base class new() method (which is one reason why you must
346 remember to call it via C<MRO::Compat> if you redefine the C<new()>
347 method in a subclass).
356 root => MyApp->path_to('root'),
359 MyApp->path_to( 'root', 'templates', 'lib' ),
360 MyApp->path_to( 'root', 'templates', 'src' ),
362 PRE_PROCESS => 'config/main',
363 WRAPPER => 'site/wrapper',
367 Note that any configuration items defined by one of the earlier
368 methods will be overwritten by items of the same name provided by the
371 =head2 DYNAMIC INCLUDE_PATH
373 Sometimes it is desirable to modify INCLUDE_PATH for your templates at run time.
375 Additional paths can be added to the start of INCLUDE_PATH via the stash as
378 $c->stash->{additional_template_paths} =
379 [$c->config->{root} . '/test_include_path'];
381 If you need to add paths to the end of INCLUDE_PATH, there is also an
382 include_path() accessor available:
384 push( @{ $c->view('TT')->include_path }, qw/path/ );
386 Note that if you use include_path() to add extra paths to INCLUDE_PATH, you
387 MUST check for duplicate paths. Without such checking, the above code will add
388 "path" to INCLUDE_PATH at every request, causing a memory leak.
390 A safer approach is to use include_path() to overwrite the array of paths
391 rather than adding to it. This eliminates both the need to perform duplicate
392 checking and the chance of a memory leak:
394 @{ $c->view('TT')->include_path } = qw/path another_path/;
396 If you are calling C<render> directly then you can specify dynamic paths by
397 having a C<additional_template_paths> key with a value of additonal directories
398 to search. See L<CAPTURING TEMPLATE OUTPUT> for an example showing this.
400 =head2 RENDERING VIEWS
402 The view plugin renders the template specified in the C<template>
405 sub message : Global {
406 my ( $self, $c ) = @_;
407 $c->stash->{template} = 'message.tt2';
408 $c->forward( $c->view('TT') );
411 If a stash item isn't defined, then it instead uses the
412 stringification of the action dispatched to (as defined by $c->action)
413 in the above example, this would be C<message>, but because the default
414 is to append '.tt', it would load C<root/message.tt>.
416 The items defined in the stash are passed to the Template Toolkit for
417 use as template variables.
419 sub default : Private {
420 my ( $self, $c ) = @_;
421 $c->stash->{template} = 'message.tt2';
422 $c->stash->{message} = 'Hello World!';
423 $c->forward( $c->view('TT') );
426 A number of other template variables are also added:
428 c A reference to the context object, $c
429 base The URL base, from $c->req->base()
430 name The application name, from $c->config->{ name }
432 These can be accessed from the template in the usual way:
436 The message is: [% message %]
437 The base is [% base %]
438 The name is [% name %]
441 The output generated by the template is stored in C<< $c->response->body >>.
443 =head2 CAPTURING TEMPLATE OUTPUT
445 If you wish to use the output of a template for some other purpose than
446 displaying in the response, e.g. for sending an email, this is possible using
447 L<Catalyst::Plugin::Email> and the L<render> method:
449 sub send_email : Local {
454 To => 'me@localhost',
455 Subject => 'A TT Email',
457 body => $c->view('TT')->render($c, 'email.tt', {
458 additional_template_paths => [ $c->config->{root} . '/email_templates'],
459 email_tmpl_param1 => 'foo'
463 # Redirect or display a message
466 =head2 TEMPLATE PROFILING
468 See L<C<TIMER>> property of the L<config> method.
474 The constructor for the TT view. Sets up the template provider,
475 and reads the application config.
479 Renders the template specified in C<< $c->stash->{template} >> or
480 C<< $c->action >> (the private name of the matched action. Calls L<render> to
481 perform actual rendering. Output is stored in C<< $c->response->body >>.
483 =head2 render($c, $template, \%args)
485 Renders the given template and returns output, or a L<Template::Exception>
488 The template variables are set to C<%$args> if $args is a hashref, or
489 $C<< $c->stash >> otherwise. In either case the variables are augmented with
490 C<base> set to C< << $c->req->base >>, C<c> to C<$c> and C<name> to
491 C<< $c->config->{name} >>. Alternately, the C<CATALYST_VAR> configuration item
492 can be defined to specify the name of a template variable through which the
493 context reference (C<$c>) can be accessed. In this case, the C<c>, C<base> and
494 C<name> variables are omitted.
496 C<$template> can be anything that Template::process understands how to
497 process, including the name of a template file or a reference to a test string.
498 See L<Template::process|Template/process> for a full list of supported formats.
502 Returns a list of keys/values to be used as the catalyst variables in the
507 This method allows your view subclass to pass additional settings to
508 the TT configuration hash, or to set the options as below:
512 The list of paths TT will look for templates in.
514 =head2 C<CATALYST_VAR>
516 Allows you to change the name of the Catalyst context object. If set, it will also
517 remove the base and name aliases, so you will have access them through <context>.
523 root => MyApp->path_to('root'),
525 CATALYST_VAR => 'Catalyst',
531 The base is [% Catalyst.req.base %]
532 The name is [% Catalyst.config.name %]
536 If you have configured Catalyst for debug output, and turned on the TIMER setting,
537 C<Catalyst::View::TT> will enable profiling of template processing
538 (using L<Template::Timer>). This will embed HTML comments in the
539 output from your templates, such as:
541 <!-- TIMER START: process mainmenu/mainmenu.ttml -->
542 <!-- TIMER START: include mainmenu/cssindex.tt -->
543 <!-- TIMER START: process mainmenu/cssindex.tt -->
544 <!-- TIMER END: process mainmenu/cssindex.tt (0.017279 seconds) -->
545 <!-- TIMER END: include mainmenu/cssindex.tt (0.017401 seconds) -->
549 <!-- TIMER END: process mainmenu/footer.tt (0.003016 seconds) -->
552 =head2 C<TEMPLATE_EXTENSION>
554 a sufix to add when looking for templates bases on the C<match> method in L<Catalyst::Request>.
558 package MyApp::Controller::Test;
559 sub test : Local { .. }
561 Would by default look for a template in <root>/test/test. If you set TEMPLATE_EXTENSION to '.tt', it will look for
566 Allows you to specify the template providers that TT will use.
570 root => MyApp->path_to('root'),
576 DBI_DSN => 'dbi:DB2:books',
587 The 'name' key should correspond to the class name of the provider you
588 want to use. The _file_ name is a special case that represents the default
589 TT file-based provider. By default the name is will be prefixed with
590 'Template::Provider::'. You can fully qualify the name by using a unary
593 name => '+MyApp::Provider::Foo'
595 You can also specify the 'copy_config' key as an arrayref, to copy those keys
596 from the general config, into the config for the provider:
598 DEFAULT_ENCODING => 'utf-8',
602 copy_config => [qw(DEFAULT_ENCODING INCLUDE_PATH)]
606 This can prove useful when you want to use the additional_template_paths hack
607 in your own provider, or if you need to use Template::Provider::Encoding
611 The L<Catalyst::Helper::View::TT> and
612 L<Catalyst::Helper::View::TTSite> helper modules are provided to create
613 your view module. There are invoked by the F<myapp_create.pl> script:
615 $ script/myapp_create.pl view TT TT
617 $ script/myapp_create.pl view TT TTSite
619 The L<Catalyst::Helper::View::TT> module creates a basic TT view
620 module. The L<Catalyst::Helper::View::TTSite> module goes a little
621 further. It also creates a default set of templates to get you
622 started. It also configures the view module to locate the templates
627 L<Catalyst>, L<Catalyst::Helper::View::TT>,
628 L<Catalyst::Helper::View::TTSite>, L<Template::Manual>
632 Sebastian Riedel, C<sri@cpan.org>
634 Marcus Ramberg, C<mramberg@cpan.org>
636 Jesse Sheidlower, C<jester@panix.com>
638 Andy Wardley, C<abw@cpan.org>
642 This program is free software, you can redistribute it and/or modify it
643 under the same terms as Perl itself.