Re: Modular Temptales

> It's in section 11.2 of the manual, "#compiler-settings".  What
> you want is "directiveStartToken".

Thanks for your prompt replies Tavis and John!  Much appreciated.


While I'm at it, I've discovered one other nagging issue...

I stopped using XSLT code generation because I spent so much time 
solving simple problems, so design went out the window!  I'm 
particularly keen to introduce a high-level of modularity in my Cheetah 
templates -- making them easy to customize.


I've learnt the hard way (I should have read the guide :) that I can't 
reuse #def's from external templates that are #include'd.  For example, 
I have an Interface.tmpl which would ideally use $declare_function() 
from another template (needed by others too).

I can think of ways around this by having a more sophisticated base 
Python class, but I'd like my templates to be mostly independent from 
the code.
Do you have any suggestions from that point of view, and how best to set 
up such modularity?


Thanks again,
Alex



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php