Re: Templates in PEAR

Joshua Eichorn wrote:

With the recent proposal of Savant the mess that templates are in PEAR has raised its ugly head again. I would like to propose that we pick one engine, Say Flexy or Xipe, and implement all the other templates in pear as wrappers and drop the rest. Either we have 1 engine and multiple api's and fix mistakes of the past or we allow competition, this double standard just doesn't cut it.

I generally agree. Dropping to means removing from the main index that is only providing the package to people who specifically ask for it. Generally I see 2 types of template engines: 1) runtime regexp replacements 2) include php code 1) phplib, it, itx, sigma The last 3 follow the same API for all that I remember and phplib is their common ancestor. 2) flexy, xipe, savant Flexy and Xipe share a common history. Their main difference seems to be the different ways they generate the php code. Savant speciality is that you dont compile at all but write php code to begin with So I see room for 2 different template engines. I see limited use in making the API replaceable, but for all but Savant (which is bound to the php syntax in the templates anyways) it seems fairly doable to support different template syntaxes. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07