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.
In reply to Re: Reusable template components with HTML::Template
by Aristotle
in thread Reusable template components with HTML::Template
by dws
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |