Re: [SMARTY] Re: [SMARTY-GENERAL] Plugindir

From: Date: Tue, 09 Apr 2002 19:56:47 +0000
Subject: Re: [SMARTY] Re: [SMARTY-GENERAL] Plugindir
References: 1 2 3  Groups: php.smarty.general 
Request: Send a blank email to php-smarty-general+get-3583@lists.php.net to get a copy of this message
That's a lot of work to put into every template if you want a blanketed output filter to apply to all of them. I'd much rather drop in a plug-in. Andrei Zmievski wrote:
On Tue, 09 Apr 2002, Andrei Zmievski wrote:
3. Pre/postfilters. Not quite sure what to do about those, since scanning all the plugin directories might be a bit costly, but then it's only done during compilation. However, if we introduce 'output' plugins then those will incur a performance penalty because they will need to be located upon every template access, unless the output plugins are specifie via something like {output type="trimwhitespace"}.
Wait, do we really need 'output' plugins? They can really easily be emulated with a combination of {capture} and modifiers and that way you can control the output of specific parts of the template. {capture name="main"} {* beginning of template *} ... ... {* end of the template *} {/capture} {$smarty.capture.main|trimwhitespace} -Andrei "PHP is like a teenage blonde walking alone in the night.. and all these newbies are lurking in the shadows.."
     -- Jani Taskinen
-- Monte Ohrt <monte@ispi.net> Director of Technology, ispi Inc.

« previous php.smarty.general (#3583) next »