A list with mixed types seem like an edge case well worth ignoring, right?
Bob Harner On Aug 20, 2011 7:54 AM, "Igor Drobiazko" <igor.drobia...@gmail.com> wrote: > Checklist, Palette and AjaxFormLoop operate on a list of objects > (SelectModel or Iterable) while the other component take only a single > value. Providing a default ValueEncoder would mean that you need to get the > first element in the list and check its type. This would probably work if > the model parameter were principal. But what if you have different types of > objects in the list? > > On Sat, Aug 20, 2011 at 3:56 AM, Bob Harner <bobhar...@gmail.com> wrote: > >> Does anyone know why half of the built-in Tapestry 5 components that >> take an "encoder" parameter are NOT set up to be able to use a >> "contributed" ValueEncoder (that is, one configured with >> contributeValueEncoderSource() in AppModule class)? >> >> The following components nicely allow the "encoder" parameter to be >> optional: >> >> Grid, GridRows, Loop, Select, Upload: >> >> But the following make you provide the encoder parameter (even if you >> have a ValueEncoder configured in your AppModule for the appropriate >> type): >> >> AjaxFormLoop, Palette, Checklist, Hidden, RadioGroup >> >> Maybe there's some subtle reason for this? >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: dev-h...@tapestry.apache.org >> >> > > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de
