* Karv Prime <karv.pr...@gmail.com> [170914 11:14]:
> ... - yet
> there's the disadvantage of the need to put artifacts into the markup which
> then get replaced by the wanted content
You have to do that anyway, you just use different artifacts. Each
location where a substitution will occur must be uniquely identified,
whether it is <div class="summaryData"></div> or
<div>{{.summaryData}}</div>.
If summaryData has any HTML at all, then the programmer and the designer
must coordinate on styles (at least style names) anyway (the Template
Animation post glosses over this point), so there is not even a need for
the <div> wrapper; just put {{.summaryData}} and let the program supply
any necessary style or class attributes. The resulting HTML will have
one less unnecessary wrapper element.
I'm not saying the <div> wrapper can't be in the template if it is
useful for other purposes, but that it is not needed for the template
substitution, whereas it is needed as a placeholder when doing DOM
manipulation.
...Marvin
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
