Ability to nest plugin calls

No - of course it is not that easy! Tried a more complex example and it doesn’t work:

{exp:yui:load type="menu"}{/exp:yui:load}

{exp:yui:load type="tabs" ....}

{tab}
   ....
   {exp:yui:load type="calendar" ..}{/exp:yui:load}

{/tab}

{tab}
    ...
    etc.
{/tab}

{/exp:yui:load}

Take 2:

// need to decide if looking for first or last instance of the tag.
                
                // if there is another opening of this same tag before the next closing one, then look for the last tag
                
                $first_open=&strpos;($this->fl_tmpl,LD.$tag);
                $first_close=   &strpos;($this->fl_tmpl, $cur_tag_close);
                            
                
                if ($first_close<$first_open)
                   $out_point=$first_close;
                else 
                    $out_point = strrpos($this->fl_tmpl, $cur_tag_close);

Of course you can nest plugins (see Nested Plugins heading). Explain what you mean by “At the moment the system gets confused”.

You can’t nest a call to the same function in the plugin as it assumes that the next closing tag for this plugin/function is the correct one.

This works: {exp:myplugin:func1}

{exp:myplugin:func2}

{/exp:myplugin:func2}

{/exp:myplugin:func1}

This does not

{exp:myplugin:func1}

{exp:myplugin:func1}

{/exp:myplugin:func1}

{/exp:myplugin:func1}

You could argue that this is bad plugin design to want to call nested functions…

You could argue that this is bad plugin design to want to call nested functions…

Yes, lol. I didn’t catch that you were using the same method, as the tags had an additional segment. I instantly read it as calling ‘tabs’, ‘calendar’, etc. of your ‘load’ plugin. But to give specific advice, I’d need to have a better of idea of what problem you are solving that led you to try that in the first place.

Here is an example that works (because I hacked core.template.php)

http://demo.savemybacon.com/index.php/todo/yui_test

(needs login, uid: demo, password: demodemo)

Here is one without the hack

http://www.ggjump.com/index.php/site/yui_test/

Have attached plugin and template.

The simple solution to me would be to make variables for your load tag that the load tag can parse instead of calling the same tag over and over again.

Yes - just need to think if there is a case of nesting the same yui object inside itself. table within a table?

Since your plugin will control how it parses variables, that shouldn’t be a problem.

So if I used your idea of variables, what would this look like?

{exp:yui:load type="tabs" name="mytabs"}

{tab}
   exp:yui:load type="calendar" name="mycal"}
    {/exp:yui:load}
{/tab}


{/exp:yui:load}

It could look like anything you want–you’re doing the parsing afterall. One possibility:

{exp:yui:load type="tabs" name="mytabs"}

{tab}
    {load type="calendar" name="mycal"}
{/tab}

{/exp:yui:load}

Presumably this would be faster as I would only be creating one instance of the plugin class?

It would be more memory efficient since there will be fewer objects instantiated - the speed will determine more on how efficiently you parse your own variables.

Thanks for your advice. Will recode when I have the time to get my head around it!