I think we are talking at cross-purposes here. It appears to me that you are aiming to be able to do something like class overloading.
No, I've never mentioned classes.
A template would need to instantiate the template plugin object and know which methods to use.
And it's not a template plugin object. Again I never said anything about class structures; it never entered into the equation.
It's not a class, it is cut and paste of existing code, probably with zero alterations.
Even if it were feasible to move the template functions to a plugin I don't believe the advantages that you are seeking would materialise.
Well, first off, I believe it is feasible; I've already done this with the "Display Wiki Page" plugin, else I wouldn't have even brought it up. It's the simple proof of concept that shows that this would work.
So here's my last attempt at simplifying the idea I've been presenting--
1. Make a new directory in the plugins folder, called "tpl_functions" 2. Download the "Display Wiki Page" plugin, copy admin.php and the lang hierarchy over to "tpl_functions" 3. Make the appropriate changes (pathnames and plugin names) inside admin.php 4. Set the text inside the "intro.txt" (in the lang hierarchy) to "This is the tpl_functions plugin and below is the API reference" 5. Cut(not copy) all the "tpl_" functions from the current DW base code 6. Paste them into a new file called "code.php" within the "tpl_functions" directory 7. Make all templates require an include to the "code.php" at the top of their files.
No classes; again this could probably be purely cut and paste with zero modifications.
Chris, please take some time and re-read through what I had said in my previous emails, investigate the "Display Wiki Page" plugin's structure and code... because I'd rather you understand the core concept before it's just written off as "too difficult."
-- --Terence J. Grant(tjgrant@xxxxxxxxxxxx) -- DokuWiki mailing list - more info at http://wiki.splitbrain.org/wiki:mailinglist