On 02/18/2011 12:59 PM, Thiago H. de Paula Figueiredo wrote:
On Fri, 18 Feb 2011 15:45:54 -0200, Rich M <rich...@moremagic.com> wrote:
The challenge in your case is I don't believe you can dynamically
assign a component ID. I double checked myself just now, and t:id
only took a discrete ID (in 5.1.0.5), and was not happy pulling it
from a property or other dynamic means.
Static structure is not possible with dynamic component ids. I think
the issue here is forgetting the event instance and relying only on
passing information to the event handler method (in this case, using
the context).
I fully agree, my answer was convoluted in attempts to reference the
broader scope of challenges faced when dealing with the static structure
of a component enclosed within a loop. The concept of static structure,
given a full understanding, makes the proper use of components in a Loop
clear.
However, I still think for someone coming to Tapestry it is likely to
think of loops in the Java sense where each iteration is fresh
(loop-declared objects/variables are unique between iterations, etc). It
would be worthwhile to clarify the implications of static structure in
loops where users are most likely to confuse a need for dynamic behavior
with dynamic structure based on prior experiences with loops. Perhaps I
haven't found the right documentation page, but I can't readily find
much explanation of static structure and its implications in the
Tapestry site documentation on pages where I might expect it.
Regards,
Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
