Smarty

[xces]

Aloha, i have the following idea;
Currently i have a CMS with only 1 smarty object.

The structure is like this:
\_templates_c
\_templates
\code
\inc

Let me explain

When i have core functions (e.g. login) it would be like this:
\_templates_c
\_templates\core
\code\core
\inc\core

When i have the photo widget it would be like this:
\_templates_c
\_templates\photo
\code\photo
\inc\photo

etc. etc.


But now i want to be able to distribute those "widgets" to multiple sites, so i am thinking of a directory structure like this:
\_templates_c
\widget\photo\_templates
\widget\photo\code
\widget\photo\inc

So if i want to install the photo widget on a new server, all i have to do is copy the "photo" directory and all should work

Is this possible with only 1 smarty object?

[CirTap]

Hi,

with the "native" Smarty class, it'd be easier to have
/cms/templates/photo
/cms/templates/foobar
and then set $template_dir to "/cms/templates". You can then {include} and {fetch} files in your templates using a relative path, avoiding the non-portable*) "file:/full/path/to/foobar.tpl".
That'd give you two folders to copy:
/photo/*.*
/templates/photo/*.*

You may also register a "CMS" template resource which does the directory juggling for your, in case you wanna stick to one folder per "widget" with all its code. Then use
$smarty->display("cms:photo/foobar.tpl")
and
{include file="cms:photo/foobar.tpl"}

I like to have all templates in one folder structure, as it's easier (IMHO) to switch themes|skins, and "installing" a new widget, site-section or weblication is done by distributing it's folder to the various themes -- if any. I actually have much less themes then widgets, sections, or apps.

Another advatage of this is that you can ZIP 'em, give it so someone for re-design and this person has all the HTML in one place.