Re: [SMARTY-DEV] Var Templates
| From: | Tom Sommer | Date: | Wed, 16 Apr 2003 17:59:41 +0000 |
| Subject: | Re: [SMARTY-DEV] Var Templates | ||
| References: | 1 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-1200@lists.php.net to get a copy of this message | ||
On Wed, 16 Apr 2003 10:45:35 -0700 (PDT), Boots wrote:
> What I think COULD be useful is extending the include function to allow
> for partioning of a template resource into sections that can be
> individually loaded (much like config files). I have purposely chosen
> some arcane syntax because I am not trying to suggest the actual
> implementation, only to illustrate the idea:
I have no need for this, you might, which is why there are so many problems
regarding what smarty should contain
> I want to add one more problem I have with your idea: the use of
> alternate syntax. We already have braces (or something user defined) to
> imply variable expansion. Adding un-braced backticks as an additional
> expansion method just seems wrong to me.
I don't care if it's backtrics or braces, the fact of the matter is that
you cannot use Variables in config variables... without having to run
{eval #this#} or whatever the syntax is... The problem is that I want to
eval on the PHP side... thats about it, which is why all I am suggesting is
a way of quickly and *optionally* resolving embedded vars in config vars...
$smarty->config_load('main.conf', EVAL_ON);
or
$smarty->config_load('eval:main.conf');
that's about it... nothing more, nothing less..
> At any rate, I'm not convinced that the change you want is really
> forwarding the engine in any meaningful way. Then again, I've been
> known to be wrong ;).
I think it will
--
Tom Sommer, Denmark
www.tsn.dk - www.dreamcoder.dk