Corin Lawson wrote:
>
> But it gave me another idea to free my code from getCurrentZoneId method.
> I am now significantly satisfied with the following solution. It makes for
> one very lean POJO.
>
But in cases like mine, where the zone comes after the links in the markup
(which should be a q
Oh I get now...
I tried using "${component:myZone}.id" as the zone attribute of the link but
all the variations I tried just rendered something like this:
"[EMAIL PROTECTED]"
I couldn't work out how to access properties of the component. Any ideas?
But it gave me another idea to free my code f
No problem, just glad i could help :o)
Regarding the component prefix, have you tried using it ? Because it
really is just what that line says. You just have to provide the id of a
component and the expression will resolve to the component instance.
Example:
Home
This would render the pagelink
Awesome!
Sorry, I overlooked that one ... I'm just a noob :P
Thanks for sharing HugoPalma.
All that I want now is the ability do away with the currentZoneId property.
Could someone explain the component prefix of a binding expression. The
Component Parameters page of the tapestry-core guide sim
Regarding your request for the event attribute in ActionLink. Doesn't
the component EventLink solve your problem ?
http://tapestry.apache.org/tapestry5/tapestry-core/ref/org/apache/tapestry/corelib/components/EventLink.html
Corin Lawson wrote:
> Hi All,
>
> I admire Travis' ambition, but he's for
Hi All,
I admire Travis' ambition, but he's forgetting an ancient programming maxim:
be lazy! By that I mean there no need to implement your own Zone component
(or sub-component). I actually got this to work, but I'm not %100 satisfied.
So the id attribute of zone doesn't allow property expansio
