Re: Which templatesystem should I choose?

Have a look at the code, It shouldnt be too difficult to implement. (I added text parse/compiling to Flexy a few weeks ago, which is a Xipe derivative.. or was quite a while ago....) I'm sure if you sent in a patch Wolfram would be pleased to add it to Xipe. I've added comments below for how well Flexy fits.. (or misses..) - Just for information.. - Regards Alan Tommy Ipsen wrote:

Hi I've used Template_Xipe for a while now but it's not possible to save templates to a database which is a feature I badly need! Therefore I have to switch to one of the other templatesystems available and would like some help choosing between them! I need the following: - Templates can be saved in both the filesystem as well as in a db (missing in xipe) Yeap - in CVS

- Nested templates (ie. templates in templates) should be allowed like in Xipe done by defining callbacks to include subtemplates... eg. {includeBody():h}

- Caching of generated pages should be possible either built in or using the Caching class in PEAR (Xipe supports this) Up to the user - I use it with Cache_Lite, I never implemented an internal cachine layer (and was one of the reasons not to address direct includes of other

- Localisation would be nice-to-have (Xipe supports this) Got something similar to Xipe...

Furthermore I really liked that the template-logic was actually just PHP code and not a new "pseudo-scripting-language" like in Smarty but this is not essential since there is very little business logic in the templates.

What is essential though is that the templatesystem should be easy to integrate with the other PEAR packages like QuickForm, DB, Mail, Crypt, Config, I18N and Cache. I hope someone can help me choose since I would rather like to avoid spending time examining all the features of the different template systems before choosing one. Cheers, Tommy