Re: [PEPr] +1 for HTML::Template_Savant

Is this more what you where thinking...????

HTML_Template_Flexy :       (core loader + assigner)
    Flexy.php, Flexy/Assign.php

HTML_Template_Flexy_Plugin : (savant plugin provider)

    Flexy/Plugin.php Flexy/Plugin.*	

HTML_Template_Flexy_Compiler : (standard compilers)

    Flexy/Compiler.php, Flexy/Compiler/Standard ...

(other compiler backends...) HTML_Template_Flexy_Compiler_Xipe : ... eventually... HTML_Template_Flexy_Compiler_Smarty : ... eventually... HTML_Template_Flexy_Compiler_WACT : ... eventually... It may be dramatic, but proposing 'HTML_Template' as a package to replace HTML_Template_Flexy's core package may be worth while, even though it is unlikely to ever provide PHPlib/IT/Sigma etc.. It would make it considerably easier to use the Common Template API that was posted before.. Regards Alan Paul M Jones wrote:

Hi, Greg, Regarding your vote comment...

This is truly a conditional vote. Now that Alan has coded compile-less templates for Flexy, the difference between Savant and Flexy has blurred. However, there is a real need for a simple, small and fast template engine that is based on PHP only. Right now, the biggest difference between Flexy and Savant for my needs is the bulky Compiler class is part of the Flexy package, even though it would never be used. I think that in an ideal world, the Flexy package would be two linked packages, installed by default, or the minimal package that is Savant. Until this capability is supported by the PEAR installer, I see little chance of my ideal solution. Having both Savant and Flexy as different codebases in PEAR doing the same thing where Flexy is Savant+ is not a good solution. Perhaps the best solution is for me to implement this possibility in the PEAR package. To add Paul as a maintainer for Flexy would be my ideal solution, if and ONLY if Savant were installable without the Compiler class. In other words, I really need a class like Savant, but probably not two of them. Maintaining the codebases in parallel will only lead to greater chance of bugs, API issues, and divide Paul and Alan's strengths unnecessarily. I support Paul 100% in his work on Savant, and I also support Alan 100% on his integration of Savant into Flexy, so my vote would be that Alan work with Paul on developing a split of Flexy into two separate but integrated packages that build on each other, based on an amalgamation of Paul's original work and Alan's integration into Flexy. I only hope the political issues can be worked out smoothly. This may take a while to get it right, but I believe it is the best solution.

... I'm not certain what the condition is regarding Savant qua Savant. Are you saying, the vote for Savant is based on a converting Savant into a pre-Flexy or a Flexy Lite? Or are you saying we need a third package, not-Savant and not-Flexy, from which both Savant and Flexy should extend? Not trying to be obtuse, just not sure what condition is to be fulfilled for your vote. I've stated before, and I'll say again, I would be happy to collaborate on a combined PEAR template system that is free of the legacies of Xipe, Flexy, IT/X, Sigma, and PHPLIB (and Savant, if it gets voted in).

-- Can you help out? Need Consulting Services or Know of a Job? http://www.akbkhome.com