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

On Jun 10, 2004, at 3:50 PM, Joshua Eichorn wrote:

I've been crazy busy at work for the last couple days so i haven't had a time to review the code but i would point out that an interface and extension isn't the only solution.

Fair enough; when you get a chance, take a look at both sets -- they seem to follow distinctly different paths, even though we're using the same reference document (the Jausions interface model). What would other solutions be, besides interface and extension? Maybe I'm too much inside the box, I thought those were two principal ideas in OOP-like code.

What you need is a decent api and the ability to support lots of features without lots of overhead over or a really complicated api. Using other patterns then just an interface and inheiritance may be a better way to go.

It may be that they both have that; Alan's seems to incorporate more into the base class for compiler control and loading, while mine seems to incorporate more for assignment and return. I've got a "placeholder" for a compiler object that gets built and configured externally to the template object itself, while Alan has a "placeholder" for assignment objects. -- 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/