Re: Play nice! Re: Savant/Flexy/Foo template engines

Hi, Skipping almost all of it, because the important part is at the end ...

I can see very easily how Savant and Flexy would both extend from this minimalist base class and still maintain their "native" APIs in the extended versions. E.g., in Savant (this is not everything) --

Trying to provide a minimalistic base class is not really the goal, the aim is to provide a core that can provide all the features of all the engines, while keeping it to a minimum...

Aha! I think this is where my philosophical disconnect is; perhaps I have misunderstood the Jausions plan and the unification goal. I thought the idea of the Jausions interface was to allow different classes to extend from the base class using the same interface -- not to "provide a core that can provide of all the features". I understood this as given by his examples of the Smarty interface, Sigma interface, and so on. It is not Flexy, not Savant, not Smarty, but a commonality of them, and the specific systems can extend from that base interface to provide specialized features. Can Philippe, Greg, Joshua, etc. provide insight? -- Paul M. Jones Savant: the simple alternative to Smarty for PHP. http://phpsavant.com/ DB_Table: build RDBMS tables and XHTML forms in one PHP class. http://wiki.ciaweb.net/yawiki/index.php?area=DB_Table Yawiki: your collaborative online documentation system. http://yawiki.com/ Yawp: a single-file foundation for PHP applications. http://phpyawp.com/