Smarty

U.Tews · Posted: Thu Dec 31, 2009 5:54 pm Post subject:

Ups I made an error when posting.

external declared template function must be called by

{call name=test}

Checking if the function name is valid is done at run time.

Besides that regardin your cases:

A:

{function} tags are processed at compile time. the {if} is a runtime tag.
So the template function gets always compiled. If you call the function in file 2 it gets alwas executed.
Anyway it would be more usefull o have the {if} in file2 around the call. Makes the whole thing more understandable.

B:

Will drop an error message at run time as the template function definition did not get loaded for x=2.

C:

Does work.

douglassdavis · Smarty Junkie Joined: 21 Jan 2008 Posts: 541

douglassdavis · Smarty Junkie Joined: 21 Jan 2008 Posts: 541

Just wanted to remark that perhaps if there was a standard place for template libraries like there was for plugins in php files, for that case, the dynamic call syntax might not be needed.

Like function.funcname.tpl

Maybe the file could be in the usual plugins dir(s).

Or it could always look in the same dir as the template, but then the file might be more easily renamed/erased, and it could only be used by templates in the same dir (without using the dynamic call syntax)

just throwing out ideas...

U.Tews · Posted: Tue Jan 05, 2010 9:39 pm Post subject:

The requirement of the dynamic call syntax has nothing to do where the files are located or how they are named.

It is required because of the way how the general flow of template and subtemplate handling works.

It would be difficult to change that for templaste functions and for example it could not work for variable filenames of the libraries. Much more trouble than benefit.

douglassdavis · Smarty Junkie Joined: 21 Jan 2008 Posts: 541

U.Tews · Posted: Wed Jan 06, 2010 3:42 pm Post subject:

Okay, I think now I got you. But that would similar to plugins require one file for each function.

Maybe something to consider for the future....