I'm going to jump onto the Template::Toolkit bandwagon. The main package for my most recent web application, called File Exchange System, looks like this:
[...]
use base CGI::Application;
use CGI::Application::Plugin::Session;
use CGI::Application::Plugin::TT;
use CGI::Application::Plugin::Stream qw/stream_file/;
use CGI::Application::Plugin::DBH qw/dbh dbh_config/;
use Template;
[..]
That gives my CGI::Application application session handling, templating, streaming (for stable file downloads) and intelligent database handle handling.
In addition to using Template Toolkit for web applications, I also use it for the installation script -- I have configuration file templates (for startup.pl, httpd.conf, Log::Log4perl files, and a main configuration file). I use TT to fill in the blanks to create the actual configuration files, then move the completed files to the appropriate locations.
Works great.
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|