Hi, It could be LabelProvider.
ValueLabelProvider because of ValueEncoder and similiar use-case of extracting something from a value. Denis On 22.7.2011, at 23:28, Thiago H. de Paula Figueiredo wrote: > On Wed, 20 Jul 2011 06:34:04 -0300, Denis Stepanov <denis.stepa...@gmail.com> > wrote: > >> Hello all, > > Hi! > >> I have improved coercion from List to SelectModel, right now you need to >> create SelectModel for Select component, but in the situation when we know >> how to display an object from the list we can do it just by binding >> collection to the model parameter. >> >> There is a new interface ValueLabelProvider to provide a label from the >> object. The coercion will use the global messages catalog not the component >> one so it could confuse a user. > > Interestingly, I was thinking of doing the same or something very similar. :) > I'd not name it ValueLabelProvider, as it could be useful for non SelectModel > scenarios too. http://tapestry.apache.org/developer-bible.html has some > Tapestry class and method naming conventions, but I don't know which one > would be the ideal for this case. What about LabelProvider? > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
