Re: Template Proposal

Hello, As a end user, I do agree that its perhaps a good thing to have several templates systems in PEAR, but I do not agree with the presentation of Smarty been a very complicate and sophisticated system devoted only to very complicated and sophisticated works. I use Smarty now on a nearly daily basis, I'm very far form been a sophisticated developer (people from Smarty list can testify ;- ) and it really rocks. It CAN be used with a lot of functions if you need them. Nobody forces you to, and even used at a simpler level Smarty is really way cool, and its a good point in term of evolution to know that even if today in your site you don't need all the function, but the day you'll need something more complete there is not problem, juts use a higher percentage of Smarty capabilities. Even if several templates are proposed by PEAR, what would be cool on the other end is to have some kind of minimalist API for using a package with a template system, allowing the various project groups working on open source projects to allow an easier use of their packages with a PEAR compliant template system. Luc At 09:32 14/07/01 +0200, Tomas V.V.Cox wrote:

I really agree with you Martin. Smarty is marvellouse, stainless steel and high quality, but for example in most of my work only need split code from design as easy as posible, without the need of functions, configurations or set write perms somewhere in the document root. I have nothing against IT (although I think Xtpl and it use the same tags), the only thing I'm against is that it will be there with bugs and without doc. If anybody wants to do a little maintain of it, my proposal will still to replace it. I vote for allowing more than one templating system in PEAR. +2 (if you let me raise the two hands ;)