> oh, well i think i replied a little too quickly. my appologies. Why is
No worries. Too fast is better than too slow. > it your templates can't know the absolute path? It would seem to me > that either a) as the template author, you know where the templates will > be rendered to, or b) as the programmer calling the templates, you know > where the templates will be rendered to. In the former case you ought > to be able to hard code the absolute path. In the latter case, you > ought to be able to pass in the absolute path as a template parameter. It's more that the template in question that is adding the css file is generic, it's called from the master templates if you will. It personally doesn't know where the main html template is - well now I realise it can find out via template.name which does path. Yay! Further I was trying to avoid having to set "statics" if you will in each master html template stating where each is. That's a pain, and not very (to use the ultimate programmers curse) efficient. But thanks yet again! Much appreciated. - Steve _______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.template-toolkit.org/mailman/listinfo/templates
