I don't think it's about having two kinds - maybe the delimiters should instead be user-definable parameters to the ->new() function?
Both have theis pro's and cons:
"<>" AND "<!-- -->" ONLY!:
[+] Forces people to code in a unified style, easy to read. Consistensy is often good.
[-] You are often forced to break HTML-rules when creating templates, thus sort of spoiling the idea of templates that are easy to create in visual editors, and easy maintain...
ALL USER DEFINEABLE:
[+] You can have your templates as VALID HTML!
[-] People might start using ~" and screw the idea this way, or at least get a bad impression of template-driven development.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It makes me feel really dirty to do something like:
<INPUT TYPE=TEXT NAME="THING" VALUE="<TMPL_VAR NAME=STUFF%gt;">
Is there any way that you can provide an alternative to avoid the characters
< and > within tag attributes?? how about:
<INPUT TYPE=TEXT NAME="THING" VALUE="??TMPL_VAR NAME=STUFF??">
or something.
hrm, that didn't look quite right, lets try again...
Instead of:
<INPUT TYPE="TEXT" NAME="THING" VALUE="<TMPL_VAR NAME=STUFF>">
how something like:
<INPUT TYPE="TEXT" NAME="THING" VALUE="??TMPL_VAR NAME=STUFF??">
Why we need to support two kinds of TMPL_VAR if we can make the same things with only one? I think that we should keep the syntax simple
I don't think it's about having two kinds - maybe the delimiters should instead be user-definable parameters to the ->new() function?
Both have theis pro's and cons:
"<>" AND "<!-- -->" ONLY!:
[+] Forces people to code in a unified style, easy to read. Consistensy is often good.
[-] You are often forced to break HTML-rules when creating templates, thus sort of spoiling the idea of templates that are easy to create in visual editors, and easy maintain...
ALL USER DEFINEABLE:
[+] You can have your templates as VALID HTML!
[-] People might start using ~" and screw the idea this way, or at least get a bad impression of template-driven development.