Smarty

[eadz]

Hi there,
I would like to make a function that acts like a section, but the section isn't a plugin so I can't look to it for an example. How would I write a function plugin that works exactly like {section} {/section}? I.e. loops, and smarty code inbetween works as normal.

[andre]

This is not possible yet (as far as I know). But newest CVS version has support for an additional function parameter which can be used for loops. I don't know anything about it yet but perhaps you want to have a look.

[eadz]

[messju]

yes i added this recently. but i'm very indifferent if i should keep it the way it is. i think >98% of block-functions have no need for it, so i wonder if i should make it optional and not default for all block-functions, since it introduces slight overhead (really very very minimal, but a few cycles overhead nontheless).

this means: use it with caution, it's unstable/experimental!

i'm pretty sure the prototype for the repeatable block will stay: smarty_block_foo($params, $content, &$smarty, &$repeat)
but maybe blocks should not be repeatable by default, but this should be specified with register_block() (defaulting to not repeatable).

this would mean, register_block() would become:
function register_block((string)$name, (mixed)$implementeation, (bool)$cacheable, (bool)$repeatable)

if it becomes that way, then you cannot use $repeat with auto-loaded block-plugins, but only with ones you register yourself. but this will be the only change to it that may come.

i posted 2 stupid examples here:
http://marc.theaimsgroup.com/?l=smarty-dev&m=105084930710497&w=2

see $repeat as the conditional of a while loop. if your block-functions sets $repeat to true, it is called again, with new $content, else the block function is done. that's all about it.

[boots]

@messju:

what if the plugin for blocks was ammended:

function smarty_block_foo($params, $content, &$smarty)
function smarty_block_start_foo($params, $content, &$smarty, &$continue)
function smarty_block_end_foo($params, $content, &$smarty, &$repeat)

If a plugin has a smarty_block_foo(), no repeats.

If a plugin has both smarty_block_start_foo() and smarty_block_start_foo(), then those two functions are called as appropriate. I changed $repeat to $continue for smarty_block_start_foo() to indicate that it aborts output if true (end is not called). The default would be to pass $continue=true and $repeat=false.

It may even be better as:

function smarty_block_start_foo($params, &$smarty, &$continue)
function smarty_block_end_foo($content, &$smarty, &$repeat)

since less data has to be passed.

2c

[eadz]

The reason I want to make a plugin that loops, isn't so that I can specify the number of times it loops, but so that the plugin itself can decide that.

For example

[boots]

@eadz:

Do you mean:

[eadz]

[eadz]

[boots]

@eadz:

it looks like you aren't looking for new functionality at all, but instead a different syntax.

You can easily do what you want by wrapping the appropriate code in a template and then {including} that template with parameters.

You don't like {include}? Well, you can create a plugin that internally does a $smarty->fetch($tpl).

Even though I think looping can be improved, I don't think that that is what you want.

IMHO

[eadz]

[boots]

Your plugin code seems to assume that the content is still un-executed--this is false. You can't write "dynamic" plugin code. What you can do is put the code that you want to be executed into a template and do a $smarty->fetch(tpl) from your plugin.