You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Harish Krishnaswamy <hk...@comcast.net> on 2003/06/25 16:36:58 UTC
How to specify visual attributes for components that forbid informal
parameters?
I think all components that forbid informal parameters should have a
class and id parameter unless there is another way of specifying the
visual attributes for these components. Does anyone know of one?
Thanks
Harish
Re: How to specify visual attributes for components that forbid
informal parameters?
Posted by Harish Krishnaswamy <hk...@comcast.net>.
I could do that, but for now to make life easier, I have added an id
attribute to DatePicker's button. Now I can format it to the user's
satisfaction via stylesheets.
Thanks
Harish
Mind Bridge wrote:
>Hi,
>
> The DatePicker contains two <input> tags, which is probably why it does not
>have informal parameters.
>
> The way to access and change the value with JavaScript (which is what you
>want to do, if i understand correctly) is to get the component after it has
>been rendered and call getName() on it to get its name. You should then be
>able to manipulate it via JavaScript using its name.
>
> Does this help?
>
>-mb
>
>-----Original Message-----
>From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
>Sent: Wednesday, June 25, 2003 5:55 PM
>To: Tapestry users
>Subject: Re: How to specify visual attributes for components that forbid
>informal parameters?
>
>
>Hi mb,
>
>I was talking about the DatePicker. I cannot format the button value on
>the component unless I change the code. Is there a way around it?
>
>Thanks
>Harish
>
>Mind Bridge wrote:
>
>
>
>>Hi Harish,
>>
>> Which components are you thinking of? Forbidding informal parameters
>>usually means that the component simply does not have a tag on which it
>>could apply them.
>>
>>Best regards,
>>-mb
>>
>>
>>-----Original Message-----
>>From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
>>Sent: Wednesday, June 25, 2003 5:37 PM
>>To: tapestry-user@jakarta.apache.org
>>Subject: How to specify visual attributes for components that forbid
>>informal parameters?
>>
>>
>>
>>
>>I think all components that forbid informal parameters should have a
>>class and id parameter unless there is another way of specifying the
>>visual attributes for these components. Does anyone know of one?
>>
>>Thanks
>>Harish
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>>
>>
>>
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
RE: How to specify visual attributes for components that forbid informal parameters?
Posted by Mind Bridge <mi...@yahoo.com>.
Hi,
The DatePicker contains two <input> tags, which is probably why it does not
have informal parameters.
The way to access and change the value with JavaScript (which is what you
want to do, if i understand correctly) is to get the component after it has
been rendered and call getName() on it to get its name. You should then be
able to manipulate it via JavaScript using its name.
Does this help?
-mb
-----Original Message-----
From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
Sent: Wednesday, June 25, 2003 5:55 PM
To: Tapestry users
Subject: Re: How to specify visual attributes for components that forbid
informal parameters?
Hi mb,
I was talking about the DatePicker. I cannot format the button value on
the component unless I change the code. Is there a way around it?
Thanks
Harish
Mind Bridge wrote:
>Hi Harish,
>
> Which components are you thinking of? Forbidding informal parameters
>usually means that the component simply does not have a tag on which it
>could apply them.
>
>Best regards,
>-mb
>
>
>-----Original Message-----
>From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
>Sent: Wednesday, June 25, 2003 5:37 PM
>To: tapestry-user@jakarta.apache.org
>Subject: How to specify visual attributes for components that forbid
>informal parameters?
>
>
>
>
>I think all components that forbid informal parameters should have a
>class and id parameter unless there is another way of specifying the
>visual attributes for these components. Does anyone know of one?
>
>Thanks
>Harish
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: How to specify visual attributes for components that forbid
informal parameters?
Posted by Harish Krishnaswamy <hk...@comcast.net>.
Hi mb,
I was talking about the DatePicker. I cannot format the button value on
the component unless I change the code. Is there a way around it?
Thanks
Harish
Mind Bridge wrote:
>Hi Harish,
>
> Which components are you thinking of? Forbidding informal parameters
>usually means that the component simply does not have a tag on which it
>could apply them.
>
>Best regards,
>-mb
>
>
>-----Original Message-----
>From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
>Sent: Wednesday, June 25, 2003 5:37 PM
>To: tapestry-user@jakarta.apache.org
>Subject: How to specify visual attributes for components that forbid
>informal parameters?
>
>
>
>
>I think all components that forbid informal parameters should have a
>class and id parameter unless there is another way of specifying the
>visual attributes for these components. Does anyone know of one?
>
>Thanks
>Harish
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
RE: How to specify visual attributes for components that forbid informal parameters?
Posted by Mind Bridge <mi...@yahoo.com>.
Hi Harish,
Which components are you thinking of? Forbidding informal parameters
usually means that the component simply does not have a tag on which it
could apply them.
Best regards,
-mb
-----Original Message-----
From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
Sent: Wednesday, June 25, 2003 5:37 PM
To: tapestry-user@jakarta.apache.org
Subject: How to specify visual attributes for components that forbid
informal parameters?
I think all components that forbid informal parameters should have a
class and id parameter unless there is another way of specifying the
visual attributes for these components. Does anyone know of one?
Thanks
Harish
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org