On Tue, 11 May 2004, Mark Fuller wrote: > I don't think you're saying this, but doesn't your decision ultimately mean > legibility of the template is outside the scope of H::T? On the one hand > you're saying H::T does exactly what you tell it to do. On the other hand, > if you write it legibly but don't like all the artifacts in your output, > then don't write it legibly. Is that reasonable?
That sounds ok, but I would add that if you want to write your templates in one style and see output in another then you are perfectly free to do so. Just write some code that takes the HTML from output() and modifies it to your specifications. Or, alternately, write a filter which you can pass to HTML::Template->new() to fixup the template before it's seen by HTML::Template. > Also, if the solution is to post-process the output to remove artifacts from > authoring legible templates, wouldn't it be better to author my templates > legibly with my own "NOLF" attribute and pre-process it to make it illegible > (and remove my "NOLF" attribute) before publishing it to the server. Then > the processing only occurs once instead of each time the page is served. I wouldn't worry so much about the runtime performance of a couple regular expressions, if that's all it would be. The time you spend on them will likely be dwarfed by database and network bottlenecks. Of course the only way to tell for sure would be to benchmark. Also, if you code your solution as a filter and use HTML::Template's caching then the filter will only be run once and the result used on each subsequent call. -sam ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ Html-template-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/html-template-users
