Re: [Template] Design issues

Alan Knowles wrote:

do something like isbool($this->option['debug']) => echo the message otherwise: - load a debug provider...

Sure that's fine too. It provides something out of the box. The point to be more flexible here... ;-)

I've already made error handling another provider... = default: return a testable error = default: DIE errors emited by anything kill things = option: convert DIE errors to RETURN or THROW

Yes, I saw that. Good.

I've no idea the pros/cons of doing anything with images.. - I can tell you from experience that if you dont see anything on the screen when developing , it can take a while to discover bugs.. (live servers tend to depend on syslog)

Agreed, don't we all have our little solution for debug output ;-) What I was saying is if you are using an image template engine and want to debug, your debug message may end up in the binary string of the image. Sure you'll get a broken image, but not convenient for debug, hence the proposed use of the PEAR::Log as an alternative... I think accepting the log object as $option['debug'] is the best approach because doesn't actually limit user to PEAR::Log but to any class as long as it has a "log()" method... Any chance to get the package under CVS PEAR/Template? Yeah, being a pain here ;-) -Philippe