The problem is that the component by default renders the multiple select list in a table of checkboxes??? Sounds like a special case? Why would anyone want that as a default? If informal parameters are not allowed (yes, I can read the documentation, thank you), then no css or id can be defined. Does make for a production ready component. The issue in introducing it is in the fact that the renderer has no way to access renderInformalParameters() method.
-----Original Message----- From: Jamie [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 11:33 AM To: Tapestry users Subject: Re: How to pass informal parameters using the MultiplePropertySelection renderer This seems like a mistake. I can't think of a good reason not to allow informal parameters on this component. Jamie Shing Hing Man wrote: >The javadoc says that informal parameters are not >allowed. So you can't. > >http://jakarta.apache.org/tapestry/doc/api/org/apache/tapestry/contrib/form /MultiplePropertySelection.html > >--- Karthik Abram <[EMAIL PROTECTED]> wrote: > > >>There doesn't seem to be any way for the renderer >>for >>MultiplePropertySelection to pass through informal >>parameters??? Anyone have >>any ideas? >> >> >> >> >> >--------------------------------------------------------------------- > > >>To unsubscribe, e-mail: >>[EMAIL PROTECTED] >>For additional commands, e-mail: >>[EMAIL PROTECTED] >> >> >> >> > >Home page : > http://uk.geocities.com/matmsh/index.html > >Send instant messages to your online friends http://uk.messenger.yahoo.com > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
