This project has the ambition to become a template engine a little different from all the others that exist for php.
It is planned as a static preprocessor to your template files, i.e. your templates are translated into normal php, which is then called by your application.
Why another project of this kind?The established projects have a large scope (template security, pre-filters, post-filters, ...) but their template syntax feels cumbersome. Why should I still write the HTML myself?
When I tried to adapt the HAML implementations phammable and php-haml, the code was repeling (one of it consisted of nothing more than a function 1000 lines long and a few comments). So I decided to start for myself, step by step and write code that is easy to pick up if any dev cares to join.
Some ideasthe template syntax shall ease the writing of PHP and HTML (think of something along the lines of HAML) the resulting php files should be readable, and not so full of cruft like, for instance, those of Smarty variables should not be assigned to the template engine, but the engine should rather use the scoping rules of php to access local variables
Use Patent Claims
Include Install Instructions
These details are provided for information only. No information here is legal advice and should not be used as such.