I thought about that, but the problem is that .html and .txt are used for different types of templates -- ie: those that contain html and those that don't.
Rather than getting too complex, I just didn't want to see some digression into .htm(l)
Really, I'd like to see the templates _not_ hard coded at all, but in a template array/hash that can be edited, so that sub build_category_page uses the template located at $TEMPLATES{build_category_page}, etc.
This sounds simple, but it requires a level or two of abstraction, ie: where do you keep this list, and how do you make a system for organizing the templates. Also, what do you do with templates that are called internal to routines (not a great idea, actually, but probably do exist)?
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
Rather than getting too complex, I just didn't want to see some digression into .htm(l)
Really, I'd like to see the templates _not_ hard coded at all, but in a template array/hash that can be edited, so that sub build_category_page uses the template located at $TEMPLATES{build_category_page}, etc.
This sounds simple, but it requires a level or two of abstraction, ie: where do you keep this list, and how do you make a system for organizing the templates. Also, what do you do with templates that are called internal to routines (not a great idea, actually, but probably do exist)?
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/