Or, instead of reinventing this functionality on top of a restrictive templating engine, you use one with a more powerful language such as the Template Toolkit, where you get reusability simply by defining the table template in a [% BLOCK foo %][% END %] and referring to it by [% INCLUDE foo %]. (You can pass parameters, as well. You could put the block in another file. And those are just some of the available options.)
Don't get me wrong, I used to be a fan of the restrictive approach. But at some point you realize that the templating engine really can't separate application logic from presentation logic for you, and that using a restrictive templating language just makes you jump through unnecessary hoops. I also find that if the templating language is not powerful enough, then presentation logic seeps back into the application — just like you just demonstrated.
Makeshifts last the longest.
-
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.
|