Granted, the majority of template engines use a template file-name and a set of name/value pairs.
This template engine uses neither: https://github.com/mindplay-dk/kisstpl I'm sure you won't care because it's not popular or well-known ;-) We use this at work because: 1. code-sniffer inspections and plain PHP templates are a requirement - view data dictionaries get in the way of that, and 2. dynamic template-selection is a requirement (enabling template overrides across modules etc.) and hard-coding template paths gets in the way of that. I know this is not the mainstream approach to templates ;-) -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/f9c471a2-e25a-49e9-9d20-c9840e6dfe04%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
