I consider reuse within a single project to be a sufficient win, so each project gets its own copy of whatever template fragments that project needs. This also allows per-project look-and-feel tweakage.
Fair enough, and definitely a win over hand-coding table
loops wherever they're needed, but:
- Isn't per-project presentation tweakage a CSS problem,
not an HTML problem? (Yes, I'm aware that I'm being a bit
of an ivory-tower theoretician here, and that CSS isn't a
universally applicable solution, but still.)
- Per-project templates don't seem to mix well with
global code (I presume your tableHTML function
is in a module somewhere) -- if your code changes in such
a way that it needs an updated table.tmpl,
you have to remember to change all the template copies, and
that sounds like a monumental pain in the ass if production
code is affected.
Of course, I'm just picking nits here. In general, I like
the idea.
--
F
o
x
t
r
o
t
U
n
i
f
o
r
m
Found a typo in this node? /msg me
% man 3 strfry
-
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.
|