Re: YATS (Yet another templating system)
| From: | Andrei Zmievski | Date: | Tue, 15 Feb 2000 20:30:06 +0000 |
| Subject: | Re: YATS (Yet another templating system) | ||
| References: | 1 | Groups: | php.template |
| Request: | Send a blank email to php-template+get-42@lists.php.net to get a copy of this message | ||
On Tue, 15 Feb 2000, Dan Libby wrote:
> Actually you must specify autohide="yes" if you want this behavior.
> Even then, you could always use an alt in your variables to keep it from
> hiding. Perhaps you meant the child sections also being hidden should be
> optional, but if so I wouldn't agree, as it perverts the meaning of what
> a section is.
No, I didn't mean that child sections shouldn't be hidden when the
parent is.
> not sure what this buys. Why can't it be done via PHP code? What's it
> got to do with display?
See previous discussion on this. Basically, if you have several template
files that share the same attributes (colors, fonts, etc.) it's nice to
be able to load some values from config files that are editable by the
designer.
> I toyed with this idea. Allowing embedded PHP code probably means that
> the templates will begin to look much like regular HTML files with PHP
> embedded. At that point, you've lost your separation between logic and
> display.
Well, I don't like mixing php in myself, but you need to be able to
include other templates, have some conditionals support, and so on. I am
not saying this should be part of the template engine specifically, but
a user could do eval() on the tpl_fetch().
I'm still looking over your code.
-Andrei
* I wish life had an UNDO function. *