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

From: Date: Tue, 09 Apr 2002 21:03:36 +0000
Subject: Re: [SMARTY] Re: [SMARTY-GENERAL] Plugindir
References: 1 2 3 4 5 6 7 8  Groups: php.smarty.general 
Request: Send a blank email to php-smarty-general+get-3594@lists.php.net to get a copy of this message
Andreas Kossmeier wrote:
Andrei Zmievski wrote:
Putting the output filters in the first directory would mean putting them in the Smarty's default directory, since that has to be the first one.
by limiting output filters to the default (first) plugin directory you can not seperate the application and the smarty lib (IMO very important).
I didn't imply "limiting", just be aware that if your filters are not in the first directory, it takes longer.
what about introducing a special output filter directory var, where you can specify a custom directory for these plugins (default could be the same as plugins_dir) and maybe a possibility for switching of output filters in your application, so smarty doesn't have to scan for any.
possible, unless we can figure out a way without adding more complications.
BTW: why not moving all plugin scanning into the compilation process? i think this should work for all plugins except output plugins, because adding an output filter would then mean to recompile all templates.
Are there currently any plugins (besides output) that are scanned after compilation is finished?

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