On Tue, Dec 09, 2003 at 01:07:04PM -0600, Puneet Kishor wrote:
I also include headers/footers, and code title and bunch of other things in the headers and footers. Most of the time the title of the page is dynamic precisely because it describes dynamic contents of a page. The designer should not worry about what the title is... the designer should only worry about how the <title> should look.
One of the things for which I use H::T is to get a consistent look to a site. Each page is written as a template with header and footer includes much as Cees Hek stated. Those titles are fixed per-page, and all the templates are run through the same script to get the final HTML output; not only does each page get its title, but the "related pages" links use the titles of those related pages too.
The only alternative I can see is to set up a database of some sort which would contain the title for each page. This seems silly.
interesting. Most everything you say above is what I do as well. Except, I have never run into the above problems (of course, I have run into many other problems, but that is not the purview of H::T).
I achieve consistent look and feel via css. I achieve consistent layout via H::T.
If you are loathe to use a database for just the title, well, just use a text file, or hardcode a list of titles and cherrypick. I mean, you are willing to use Perl/H::T to achieve a consistency of appearance and don't consider that silly (I am assuming that by your statement above you are _not_ using Perl/H::T to generate the content dynamically), but don't want to use dynamically allocated titles and consider that silly.
;-)
I am not saying the above to fight or to be rude... but actually to learn from what and why is that you are working the way you are... hopefully I will learn some tricks.
But it seems that the variation that you (and Cees and Karen) have specified has little to do with H::T. I mean, any tool can and will be used in ways other than the designer of that tool meant it for... the key is to balance between the tool's simplicity versus provision for all possible creative uses of that tool.
Otoh, the need for TMPL_ELSIF tags... I didn't see any need for it, but when Timm articulated it so well, it seems to me, hey, that would be real nice. Because not having it does H::T wrong... after all, H::T's goal in life is to avoid logic in display as much as possible. And having ELSIF will allow it to do that.
In any case, great discussion and input. I guess the final choice will (and should) be Sam's. Just nice to see that H::T has a future at least upto version 2.7. More than that would be like predicting the stock market.
H::T is a great program... thanks to everyone who made it (Sam and whoever else), and this is a great community... thanks to all those who have helped me when I was stuck.
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Html-template-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/html-template-users
