I've had a discussion in another forum about another templating engine
Tiny But Strong (TBS). The subject was why no templating engine was used for that project. I was convinced TBS would be a great templating engine for a system that had none. It was pointed out to me that template engines must separate business logic from the presentation of that data and that can be done without a new template language. PHP can be one on its own.
Contao addressed the templating side by restricting available options in each template and also using the shorthand and alternative php structure names (for example: foreach () ... endforeach
![Wink](images/smilies/wink.png)
. This is in no real way harder to learn then Smarties syntax that uses the PHP grammar anyway.
Interesting article:
http://www.massassi.com/php/articles/template_engines/
Quick summary: Adding Smarty does not add new functionality besides from caching. What Smarty does is adding shortend tags for php functions: {= is equal to <?php or <?php echo, and ;} to various closing tags. Adding Smarty means the file has to be parsed by Smarty first, evaluated and built again, except it takes more time and memory then without. Smarty is a way of displaying the same information in the same structure, the same way with different symbols.
I apologize for appearing so negative regarding your extension. I didn't mean to offend you and hope you don't take it that way. I do like someone took the effort of integrating Smarty, people may have a need for it even though I cannot agree. I also did not look at the quality of the code which might even be excellent. Thanks for adding the extension!
Bookmarks