Yesterday Timothy Appnel wrote:
> One way I thought this could be implemented would be to create a
> filter that not only translates the user-friendly template markup to
> HTML::Template markup, but interprets calls for filters to be applied
> (as attributes to the user-friendly tags) and places markers in the
> HTML:Template code. (i.e.
> <FILTER:lowercase>...Foo...</FILTER:lowercase>)
If the filter is something that affects what the value is -- such as
converting an amount to a different currency -- it should probably be
part of the program logic and done before being passed to the template.
Purely presentational matters are better left to CSS. For example, if
your designer decides that the 'look' of the site involves having all
product names being lower-case then he/she can do this in the template:
<span class="product"><TMPL_VAR product></span>
And have this CSS fragment in the site's style-sheet:
.product { text-transform: lowercase; }
Smylers
--
GBdirect
http://www.gbdirect.co.uk/
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Html-template-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/html-template-users
