W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

Re: [webcomponents] HTML Parsing and the <template> element

From: Adam Barth <w3c@adambarth.com>
Date: Wed, 8 Feb 2012 14:36:38 -0800
Message-ID: <CAJE5ia_Y_jZSdiH1w0icR+tUWNsHqyptpsQfDcU+qtyKz7Q=VQ@mail.gmail.com>
To: Erik Arvidsson <arv@chromium.org>
Cc: Dimitri Glazkov <dglazkov@chromium.org>, public-webapps <public-webapps@w3.org>, Henri Sivonen <hsivonen@iki.fi>, Ian Hickson <ian@hixie.ch>, Rafael Weinstein <rafaelw@google.com>
On Wed, Feb 8, 2012 at 2:20 PM, Erik Arvidsson <arv@chromium.org> wrote:
> On Wed, Feb 8, 2012 at 14:10, Adam Barth <w3c@adambarth.com> wrote:
>> ... Do you have a concrete example of
>> where nested <template> declarations are required?
>
> When working with tree like structures it is comment to use recursive templates.
>
> http://code.google.com/p/mdv/source/browse/use_cases/tree.html

I'm not sure I fully understand how templates work, so please forgive
me if I'm butchering it, but here's how I could imagine changing that
example:

=== Original ===

<ul class="tree">
  <template iterate id=t1>
    <li class="{{ children | toggle('has-children') }}">{{name}}
      <ul>
        <template ref=t1 iterate=children></template>
      </ul>
    </li>
  </template>
</ul>

=== Changed ===

<ul class="tree">
  <template iterate id=t1>
    <li class="{{ children | toggle('has-children') }}">{{name}}
      <ul>
        <template-reference ref=t1 iterate=children></template-reference>
      </ul>
    </li>
  </template>
</ul>

(Obviously you'd want a snappier name than <template-reference> to
reference another template element.)

I looked at the other examples in the same directory and I didn't see
any other examples of nested <template> declarations.

Adam
Received on Wednesday, 8 February 2012 22:37:41 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:50 GMT