Re: 2.0: mustache template engine?
Reply #16 –
I think that is more that 99% of the edits are done either in the header area or in the footer so that they are visible in any page (and both are in index.template.php).
Re: 2.0: mustache template engine?
Reply #18 –
A question I just thought of while working on an addon for a client: How would template layers work in Twig et al? Genuinely curious, as I don't know how to work with any template engine other than PHP.
Re: 2.0: mustache template engine?
Reply #22 –
Please explain to me exactly what advantage this brings. Syntax substitution is all I've seen really.
Re: 2.0: mustache template engine?
Reply #23 –
Please, read the topic from the beginning and I made at least a couple of arguments that are not at all about syntax substitution.
Re: 2.0: mustache template engine?
Reply #28 –
Apart from the template engine, that could be whatever, I think we can agree on two things:
1) lots of logic should disappear from the templates (pretty much like queries disappeared from the controllers),
2) admins that are not insterested in learning anything deserves something that doesn't crash their forums incase of mistakes.
These are tge two current problems.
1 can be addresses withot a template engine (and actually I think it would be better to solve it before thinkinf about anything else).
2 would definitely require an approach similar to that of a template engine, but is nor an immediate concern.
Based on that, I think the first thing to do is solve 1, with agreed c9nventions and conding styles, something like do not use any other variable apart $context in the template files.
Re: 2.0: mustache template engine?
Reply #29 –
Sounds like a good plan. After one is handled you can better decide how to handle two if it's even still much of a problem.