>> 3) This component takes an "encoder" parameter but does not support a>> >> ValueEncoder configured to be provided automatically by Tapestry. It would be nice to migrate all of the collection based components to a generic form.
With the generic information you could also pick the right value encoder. private Checklist<Fruit> userChecklist; would use the configured ValueEncoder<Fruit>. Josh On Mon, Nov 7, 2011 at 1:12 AM, Igor Drobiazko <[email protected]> wrote: > hi, > > On Sun, Nov 6, 2011 at 5:24 PM, Bob Harner <[email protected]> wrote: > >> Hi everybody, >> >> I've been meaning to bring this up for a while now. The new-for-5.3 >> Checklist component has -- for me -- a couple of minor annoyances: >> >> 1) The label for each checkbox is positioned *before* (that is, to the >> left of) the checkbox. I think it is much more common to want the >> label *after* (to the right of) the checkbox. >> > > Can't it be done by overriding the CSS? > >> >> 2) The <label> for each checkbox is not connected to the checkbox with >> a "for" attribute, so you can't click on the label to check or uncheck >> the box. >> > > Fixed. https://issues.apache.org/jira/browse/TAP5-1747 > >> >> 3) This component takes an "encoder" parameter but does not support a >> ValueEncoder configured to be provided automatically by Tapestry. >> >> > This is done for the same reason Palette component doesn't provide a > default encoder. We discussed that issue some time ago in the developers > list. > > > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
