Jesse Kuhnert a écrit :
Look at the "How client ids are generated" section here:
http://tapestry.apache.org/tapestry4.1/ajax/basics.html
It's all covered in excruciating detail. The gist of it is that you do
this:
public void renderSomething(){
super.renderIdAttribute(writer, cycle);
}
an
Look at the "How client ids are generated" section here:
http://tapestry.apache.org/tapestry4.1/ajax/basics.html
It's all covered in excruciating detail. The gist of it is that you do
this:
public void renderSomething(){
super.renderIdAttribute(writer, cycle);
}
and everything else gets ha
Igor Drobiazko a écrit :
Well, your component looks somehow strange to me. I don't see what it
should
do.
However id="checkbox" is written when your contained checkbox is
rendered.
That's expected behavior. Your own component does nothing except
registering
to the group. So why do you expect
Well, your component looks somehow strange to me. I don't see what it should
do.
However id="checkbox" is written when your contained checkbox is rendered.
That's expected behavior. Your own component does nothing except registering
to the group. So why do you expect id="ckL1"?
On 7/25/07, #Cyril
Igor Drobiazko a écrit :
It is inpossible to help you without having a look into your
GroupableCheckbox.java and GroupableCheckbox.html
Please post it.
Ha! That's another story, a more complex problem ;-)
After relearned Ids concept, I can talk to you about the component
GroupableCheckbox which
It is inpossible to help you without having a look into your
GroupableCheckbox.java and GroupableCheckbox.html
Please post it.
On 7/25/07, #Cyrille37# <[EMAIL PROTECTED]> wrote:
Igor Drobiazko a écrit :
> Cyrille,
>
> please provide your sources. Otherwise we have to use our glass sphere
:)
But
Igor Drobiazko a écrit :
Cyrille,
please provide your sources. Otherwise we have to use our glass sphere :)
But I do not need to debug my source, I just need more memory ;-) I do
not remember some tapestry syntax.
I think I'm handsaking component's ids in my brain.
Is that syntax definition r
Cyrille,
please provide your sources. Otherwise we have to use our glass sphere :)
On 7/25/07, #Cyrille37# <[EMAIL PROTECTED]> wrote:
Andrea Chiumenti a écrit :
> ciao,
> the fact is that tapestry uses the form form['componentname'] , so
> for
> Tapestry name is sufficient to specify ur id
Well this question should be addressed to Jesse
On 7/25/07, #Cyrille37# <[EMAIL PROTECTED]> wrote:
Andrea Chiumenti a écrit :
> ciao,
> the fact is that tapestry uses the form form['componentname'] , so
> for
> Tapestry name is sufficient to specify ur id u should use
> id="clientId:yourCom
Andrea Chiumenti a écrit :
ciao,
the fact is that tapestry uses the form form['componentname'] , so
for
Tapestry name is sufficient to specify ur id u should use
id="clientId:yourComponentId".
But why the shortest way jwcid="[EMAIL PROTECTED]" does not create
a html element with a id="myCo
ciao,
the fact is that tapestry uses the form form['componentname'] , so for
Tapestry name is sufficient to specify ur id u should use
id="clientId:yourComponentId".
Hope this helps.
kiuma
On 7/25/07, #Cyrille37# <[EMAIL PROTECTED]> wrote:
Hello
I'm writing my first "complex" component :
Hello
I'm writing my first "complex" component : GroupableCheckbox (not same
behaviors as CheckboxGroup).
The question is about the component id. To define the id of the
component I think to use the text before the @ in the jwcid but it does
work, I had to add an id attribute :
does not wri
12 matches
Mail list logo
