bye bye patTemplate

[kmekc]

The question is, how the template is transcripted.

Often they just use pattern search. Modern template engines use a precompile to php code (smarty) and cache the precompiled template. So the parser just checks if there is a precompiled template and then include this one. In the precompiled template itself the template variables are replaced by php variables so there is no need for pattern search, just echoing the variable.

This seems to be the most performant use of a template engine. If TBS uses this approach it should be as performant as every other template engine with the same approach.

[absalom]

The question is, how the template is transcripted.

Often they just use pattern search. Modern template engines use a precompile to php code (smarty) and cache the precompiled template. So the parser just checks if there is a precompiled template and then include this one. In the precompiled template itself the template variables are replaced by php variables so there is no need for pattern search, just echoing the variable.

This seems to be the most performant use of a template engine. If TBS uses this approach it should be as performant as every other template engine with the same approach.

TBS already has caching plugins so theoretically it could end up utilising the J! cache system or working alongside it. Precompilation is something that is current or close to release, from what I've been reading.

Edit: I've found how ModX interacts with TBS - TBS is an addon in replacement of the Smarty engine deployed with ModX.
http://modxcms.com/forums/index.php/topic,5110.0.html

The problem in J!'s case is that there is no means to replace (or add) a second template engine.

Edit 2: And from what I hear, the Core team can't or won't integrate a second engine anyway..