On Sun, 27 Feb 2011 21:59:38 -0300, Tom van Dijk <t...@tvandijk.nl> wrote:
Op 28-2-2011 1:08, Thiago H. de Paula Figueiredo schreef:
On Sun, 27 Feb 2011 19:42:35 -0300, Tom van Dijk <t...@tvandijk.nl>
wrote:
the list of "A" items. I very quickly ran into problems with the
combination of nested zones, loops, forms and actions, partially
because the client IDs of the zones and forms tended to change and
after I edited something, the page was broken.
Provide explicit ids for all components and this problem should go away.
Um, it became ZoneId_1 and ZoneId_2 and so forth. Or do I miss something
here?
I forgot to mention: if the Zone (or any other component) is located
inside a Loop or Grid, you cannot just give a static id. Something like
this:
<li t:type="Loop" t:source="objects" t:value="object">
<div t:type="Zone" id="zone-${object.id}">...</div>
</li>
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
