Re: [SMARTY] SMARTY not for WYSIWYG designers?
| From: | Paul Lockaby | Date: | Wed, 26 Feb 2003 04:26:26 +0000 |
| Subject: | Re: [SMARTY] SMARTY not for WYSIWYG designers? | ||
| References: | 1 | Groups: | php.smarty.general |
| Request: | Send a blank email to php-smarty-general+get-8205@lists.php.net to get a copy of this message | ||
Dr Tarique Sani wrote:
Going thru the docs I noticed most examples follow the include header.tpl and include footer.tpl way. If the templates are to be edited in WYSIWYG editor then having a combined header and footer which gives the designer a closer representation of the final page is the way to go... ... I did find a example in the wiki BUT my question : "Is SMARTY templates not meant/aimed for designers?" Cheers TariqueCheck out this thread: http://marc.theaimsgroup.com/?l=smarty-general&m=104567031700608&w=2 If you look deeper into it, there are some methods described to use one "common" template and then including the appropriate subtemplate. For instance, you would put all your common stuff into index.tpl which would have an include in it like this: {include file=$b_page} and then you would assign the name of the template to include into the main template as b_page. And to make sure they all get different cache and compiled, be sure to pass unique cache and compile ids when you display them. Look here for more info on how to do that: http://smarty.php.net/manual/en/api.display.php Hope that helps! ~Paul -- Paul Lockaby paul@paullockaby.com http://www.paullockaby.com