Re^2: How to do tables

One thing I've done a few times (when not using Mason (or recently, other not-Perl not-CGI mechanisms)) is to let the TT source ride along after the __END__ marker of the CGI's source. Then you just my $tmpl_text = do { local $/; <DATA> }; to slurp it in before handing it to $tmpl->process( \$tmpl_text );

You could also get fancy with Inline::File and store separate templates after separate markers, but at that point you're probably approaching being better off storing them elsewhere as separate files.

Comment on Re^2: How to do tables Select or Download Code

Replies are listed 'Best First'.
Re^3: How to do tables by Rhandom (Curate) on Jan 23, 2007 at 21:18 UTC
The CGI::Ex::App framework which I use allows you to either return a file name or a reference to a scalar containing the template. It then passes the value along to CGI::Ex::Template which is Template Toolkit compatible and will process either a filename or a reference to a scalar. This allows for easy prototyping in a single file, and then the capability to move items out to separate files later. `sub main_file_print { 'my_content/my_script/main.html' } sub otherstep_file_print { return \ qq{<html> My template follows here. </html> }; }` [download] my @a=qw(random brilliant braindead); print $a[rand(@a)];	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: How to do tables
by Rhandom (Curate) on Jan 23, 2007 at 21:18 UTC

CGI::Ex::App

CGI::Ex::Template


sub main_file_print { 'my_content/my_script/main.html' }

sub otherstep_file_print {
    return \ qq{<html>
My template follows here.
</html>
};
}
[download]

my @a=qw(random brilliant braindead); print $a[rand(@a)];

[reply]
[d/l]