Mark threads with "[2.0]" for discussions about features in the longer-term future, "[1.6]" is for short-term. This is not the place for general discussions or plugin or template requests. Only features that are approved to happen by the core team should be listed here for better structuring.
- Core Developer
- Posts: 30014
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
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.
- Posts: 50
- Joined: Sun Dec 26, 2010 5:58 pm
Seems I kicked something off here.
- Posts: 4598
- Joined: Sun May 02, 2004 3:04 pm
@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: https://gist.github.com/2358670
Its purpose is to boost and minify JS and CSS files into one file each.