Mike Orr <iron@...>:
> The current way is to manually compile the templates using
> cheetah-compile. Why isn't this an option,
Hm. Maybe it is. I've just gotten so used to PHP...
> besides requiring a minor
> inconvenient step whenever you make changes?
I guess that's it. Being used to PHP (and Python, for that matter),
I don't care much for compilation... But it's not that much of a
problem, I guess.
> Two advantages of cheetah-compiling the templates are:
> 1) It does a certain level of error checking, so you know beforehand
> your templates won't bomb out when requested, at least for certain
Well, I tend to take a look at my web pages anyway, so I don't see
this making much of a difference. But it doesn't hurt, I guess.
> 2) It cuts out the overhead of compiling and byte-compiling the servlet
> at request time. Webware may be able to cache *.tmpl files using its
> own caching mechanism, but that wouldn't affect the first time the
> servlet is called.
Well, as I said, I tend to look at my web pages to see if they're OK.
While doing that, I automatically compile the template, no? I.e. the
first time will always be my problem :)
The only real advantage I've found of manual compilation is that if I
edit a header file or something similar, this won't show in the pages
themselves, since they are already compiled and cached. (Talking about
PSP now.) IMO this is a great weakness, compared to e.g. PHP. It means
that I have to run find/touch or something to update all my files when
I edit a common include file, and that wreaks havoc with the
modification dates, of course... The modification date (of the tmpl
file) wouldn't be affected by manual recompilation, of course.
(If the caching mechanism of PSP is smarter than what I've discovered
so far, I apologise... :)
Magnus Lie Hetland The Anygui Project