Page 4 of 4

Re: [2.0] Smarty3

Posted: Wed Nov 30, 2011 10:13 pm
by garvinhicking

I cannot imagine that they will drop the old foreach syntax. This is one of the most important syntaxes of Smarty anywhere; the developers surely cannot drop such a central notation in favor of a harder to understand syntax. If people would want such an notation, they would use PHP and not a template processor.
Start working just to drop '@' does not make real sense to me. I like the shorter ALL CAP constant also, but it is an extra parsing and I am not sure it is in general a good idea to bend notations of third party software. If we could stay clean here, would allow us to broad the base of developers...
But we'll have to keep the old $CONST replacement for some longer time to come, so we also won't be able to really benefit from those changes right now. I'd like to hear other people about how they feel on $CONST vs. $smarty.const. notation and readbility.


Re: [2.0] Smarty3

Posted: Sat Dec 03, 2011 1:18 pm
by Manko10
Seems I kicked something off here. :-)

Re: [2.0] Smarty3

Posted: Fri Apr 13, 2012 11:11 am
by Timbalu
@Garvin, we should purge the Smarty3 branch on GitHub, as it is outdated and confusing.

This might be of special interest coding Serendipity templates....
I just found a very nice Smarty Plugin by Rodney Rehm.
Its called Smarty Booster Plugin and can be found here:
Its purpose is to boost and minify JS and CSS files into one file each.