Hi
You are right.
There seems to be situation when you get the right id, but I just came
across one where this is not the case. After that I take a short
look at the tapestry code and I wonder why my sugested solution ever worked.
My Question is, can anyone give me a hint how to implement dojo wrapper
widgets in a correct way, that depend on other components.
Eg.: I just wanted to create a Tooltip component with the dojo tooltip
that can be used an any other tapestry component, but
therefore I would need to have the client id of the component, I
want to show the tooltip for.
I think this is realy a demand, because other users I am in contact
with, start making hacks around pseudo css classes to get the ids back
in return.
kind regards,
Robert
Roberto Ramírez Vique schrieb:
I'm using this method (also using tap 4.0.2), but seems to be not
working.
For me it gets the next supposed "id", I mean, if I have a component
named
legalId the id in the page is legalId but when I executed the method
I get
: legalId_0 ... probably I make any mistake...
thanks,
robert
On 11/5/06, Karthik N <[EMAIL PROTECTED]> wrote:
yes i did use idPath for the hidden field.
but i'm using tapestry 4.0.2 - could that be the reason i'm seeing
different
results than you are?
On 11/5/06, Patrick Moore <[EMAIL PROTECTED]> wrote:
>
> did you assign the hidden field's id using idPath?
>
> Also I am using the 4.1.1 SVN build.
>
> I am having some success with this method (borrowed from another's
> email) in finding the unique ids but I haven't throughly tested it
> yet:
>
> public String getUniqueId(AbstractComponent component) {
> return getRequestCycle().getUniqueId(
> TapestryUtils.convertTapestryIdToNMToken(component.getIdPath()));
> }
>
> Hopefully there is a better solution soon!
>
> -Pat
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
