Re: template solutions?

The 'security' angle is the only one I consider terribly valid, an was what I had in mind when I said I can't think of too many reasons why a packaged' template' solution is in order. Obviously it is for you. I still believe that in most cases it doesn't make much sense to use one, for most people, because it's limiting you to a subset of a powerful language, and the implementation can be slower. Smarty is on the right track by compiling the templates to PHP and cacheing them. What I'd *love* to see is a template system which is portable between various platforms (JSP, CF, PHP, Perl, VBScript). That would, imo, make it worhtwhile for people to learn *one* templating system that would be cross-platform. On Tue, 1 May 2001, Christian Reiniger wrote: > On Monday 30 April 2001 21:02, Steven Haryanto wrote: > > At 5/1/2001 01:43 AM, Michael Kimsal wrote: > > >I understand completely what you're getting at already, but PHP is > > >designed to do what you're asking to do. > > > > > >I know there are valid reaons for stripped down implementations, but > > > can't think of too many. > > > > Clean separation of content and presentation? That is one strong > > point (for some people anyway). > > Well, whether you write > <p>Hello <?= $User ?>, how are you?</p> > or > <p>Hello {{ USER }}, how are you?</p> > > doesn't really matter I'd say. > > > Ease of use? I want to let *other people* customize the web page to > > some extent, but surely do not want to require them to learn PHP. > > Also in this regard. > > -- > Christian Reiniger > LGDC Webmaster (http://sunsite.dk/lgdc/) > > CPU not found. retry, abort, ignore? > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net > For additional commands, e-mail: php-general-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net >