Re: [SMARTY] Giving users the chance to create their own skins

From: Date: Wed, 19 Mar 2003 13:59:54 +0000
Subject: Re: [SMARTY] Giving users the chance to create their own skins
References: 1  Groups: php.smarty.general 
Request: Send a blank email to php-smarty-general+get-8740@lists.php.net to get a copy of this message
John W. Holmes wrote: >> I was wondering if anybody tried making a meta-templating system to >> let final users customize their own templates. >> I would like to let them change the HTML but I do not want to let >> them mess with Smarty's tags. >> It would be nice to have a sort of meta-language to let them put >> placeholders instead that would then be substituted by actual >> predefined Smarty tags. > > So you want a templating engine for Smarty? Maybe call it Smarter? > Smarty tags are already placeholders, why would you replace them with > something else? The whole idea of Smarty is that you can let users or > whoever modify the .tpl files with the Smarty tags and it won't affect > the logic of your page. There shouldn't be any logic in your Smarty > code other than maybe deciding if something should be displayed or > not. Yes, you could be right about letting them play with the full Smarty syntax, but I'm worrying they could break something. I should give another read to the docs about how to disable {php} tags and other potentially dangerous stuff in the templates. > I agree with the poster from a few days ago who said that Smarty is > getting too bloated and having too much logic. Maybe there should be a > "Smarty-Lite" that'll go back to just having sections, loops, and > replacements... vote? A "lite" version is not really needed. I guess that by deleting some of the default plugins and disabling all the dangerous stuff I could go with it. -- Valerio Santinelli One Man Crew Gaming Community (http://www.onemancrew.org) My Lab (http://tanis.hateseed.com) HateSeed.com Founder (http://www.hateseed.com) In Flames Italia Webmaster (http://www.inflames.it)

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