I can't speak for jdtoronto, but i am pretty sure that he
was talking about keeping the HTML and Perl seperate, but
in the same text file - i.e., put the template in the DATA
section. I agree that this is nice for small quickies, but
for anything serious, you should go ahead a seperate the
code and template into two (or more) text files.
So then the question is (again) - why not put the code and
template in the same text file? Because you will most likely
end up having to seperate them in the long run when
scalability rears it's ugly head. (please see 3Re: HTML::Template - complex sites
for a technique for dealing with a more complex template
structure.)
jeffa
L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)
-
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.
|
