I actually asked this same question last week (look for "zones and blocks
inside components"), but haven't received an answer yet. Someone said this
in a thread some time ago, but zones are really one of the few things that
feel very unfinished in Tapestry 5. Like you'll be building your application
and everything is really awesome... until you try to use zones :p
How's everyone else not running into this issue? Are you all just not using
zones?
Mike Oestereter wrote:
>
> Hi
>
> I've got a Person component that gets rendered within a loop.
> Inside the Person.tml I've got a zone (zony) and an actionlink that should
> update that zone.
> A click on any (not the first) of the rendered ActionLinks incorrectly
> updates the first zone "zony" (and not, say, "zony_1") - it appears that
> the
> mapping is incorrect:
>
> Tapestry.init({"zone":["zony","zony_0","zony_1"],"linkZone":[["email","zony"],["email_0","zony"],["email_1","zony"]]});
>
> I think is should be rather..
>
> Tapestry.init({"zone":["zony","zony_0","zony_1"],"linkZone":[["email","zony"],["email_0","zony_0"],["email_1","zony_1"]]});
>
> I don't know how to fix it.
>
> I tried to move the actionlink around (not in a block) - not luck. I also
> tried implementing my own id scheme but I can't specify a property for
> t:id
> inside t:zone.
>
> Here are sniplets..
>
> Person.tml:
> <t:zone t:id="zony" visible="true">
> <t:delegate to="activeBlock"/>
> </t:zone>
>
> <t:block t:id="b1">
> <t:actionlink t:id="email" context="prop:person.id" zone="zony">contact
> me</t:actionlink>
> </t:block>
>
> <t:block t:id="b2">
> ....
>
> CallingPage.tml:
> <t:loop source="members" value="member">
> <t:person personRef="member"/>
> </t:loop>
>
>
> Any help would be appreciated
>
> Thanks
>
>
--
View this message in context:
http://www.nabble.com/zone-ids-in-component-within-form-tp18046195p18057607.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
