My take:
Because otherwise tapestry has trouble assigning client ids to zones at
different stages of the partial render. This makes it hard to control
the behaviour unless you set both.
p.
On 10/08/2012 8:34 AM, bhorvat wrote:
Well like it says in the subject, why should we specify both normal id and
the t:id. I know that the latter is for the tapestry where the first one is
for the client, but why is not that set by default in tapestry if it is that
important, and I take it that it is because some of my code wont work
without. For example
<t:form>
<t:jquery.slider t:id="percentageSlider" t:value="percentage"
t:zone="zonePercentage"
t:params="sliderParams" />
</t:form>
<t:zone t:id="zonePercentage" id="zonePercentage" t:update="show">
<div class="itcTxt">${percentage}%</div>
</t:zone>
without id="zonePercentage" the event wont be triggered.
thanks all
cheers
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Why-should-we-specify-t-id-and-id-for-the-zone-tp5715208.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
