On Mon, 11 Aug 2014 10:09:07 -0300, Muhammad Gelbana <m.gelb...@gmail.com>
wrote:
Why don't Tapestry allow developers to *optionally* assign client-side
IDs to components before rendering them ? With every iteration in a loop
and
with every page render...
What components are you talking about? Most components, if not all, which
have an HTML id autogenerated already have an 'id' or 'clientId' parameter
you can use to provide your own id. If there's some component which
doesn't, please let us know.
Reading documentation sometimes seems like an old, forgotten art . . . :P
From your previous thread, you seem to be talking about Zone. Here's the
5.4 version of its JavaDoc:
http://tapestry.apache.org/5.4/apidocs//org/apache/tapestry5/corelib/components/Zone.html.
Check the Component Parameters section.
Name: id
Type: String
Description: If bound, then the id attribute of the rendered element will
be this exact value. If not bound, then a unique id is generated for the
element.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
