Re: [SMARTY-DEV] Re: Var Templates
| From: | Tom Sommer | Date: | Wed, 16 Apr 2003 13:40:15 +0000 |
| Subject: | Re: [SMARTY-DEV] Re: Var Templates | ||
| References: | 1 2 3 4 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-1196@lists.php.net to get a copy of this message | ||
On 16 Apr 2003 08:34:56 -0500, Monte Ohrt wrote:
> I like the idea of using a custom resource to handle these kinds of
> feature requests, keeping it out of the core. Example:
> {config_load file="eval:my.conf" section="foo"}
> But, smarty does not (yet) support custom resources on config files,
> only templates. This is something I've been wanting to work on for some
> time but it is low priority. With this, other nifty things could be done
> like supporting other config file formats, or even writing back to them:
> {config_load file="ini:my.conf"}
> That could be a custom resource to load php.ini formatted files.
Hmm, interesting, but I need it on the PHP side :)
( I don't know if your example would also be usable as
config_load('eval:myconf.ini');
Did you read my first post in this thread, do you have any comments on it?
Because as far as I see it won't do anything to performance if it's an
extra flag/argument that toggles this in config_load();
Is my feature request really that hard and unwanted to implement? It's
extremely useful for assigning template paths, like I have...
text_reply = "<img src="{$THEME_PATH}images/this.jpg">"
and so *I NEED* to be able to use a dynamic path to point at the correct
image...
--
Tom Sommer, Denmark
www.tsn.dk - www.dreamcoder.dk