great answer christian,
quote:
"brings another caveat: If the actionLink from my example would be
specified in the template before the zone this wouldn't work. The zone's
clientId would be "null" because the zone hasn't been rendered, yet… You
could add some more advanced tricks with Heartbeats and
@HeartbeatDeferred but… I guess you'll just stick with solution #1"
this is exactly what i meant by my answer and a bit of a pet hate.
Is there any drawback to ALWAYS setting t:id & id so they are equal?
If not, i may create a patch/custom zone component until tapestry
catches up .. ?
On 12/08/2012 6:19 PM, bhorvat wrote:
Wow amazing reply.
Thanks a lot Christian this was perfect answer to my question and it gave me
a chance to learn and understand a few things about tapestry.
I really appreciate it.
All the best
Boris
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Why-should-we-specify-t-id-and-id-for-the-zone-tp5715208p5715289.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
