Yes, i know this could become a religious warfare, but i like to discuss
this anyway.
In the "Evaluate Zend Framework thread" Alfonsas Cirtautas posted this
simple line:
> smarty ?
I think that Smarty is obsolete, unclear and blocking major enhancements
like advanced caching techniques and more flexible object orientation.
The "precompiling" stuff is unnecessary if you use native php and the
advancements for designers are minor.
Although there is, with exception of dreamweaver with special plugins,
no current IDE which can handle the oxid-special smarty codes properly.
Don't try to user Eclipse Aptana Plugin with oxid .tpl files, it will
consume almost all of your cpu time and it will be slow anyway. But that
a issue of Aptana.
I know this page is a little bit bashing:
http://nosmarty.net/
The arguments are plausible and for myself, i think smarty is not the
2009 century solution for templating engines.
The smarty code itself is a relict of the PHP 4 age and isn't really oop
or flexible anyway.
I would suggest to implement some alternative engine or a new selfmade
engine, and - for a "quick" solution - implement the possibilty to use a
own engine.
And yes, i know that it will be a major change and a lot of people would
be annoyed if there is no smarty anymore.
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
