Hi Thiago, I just thought of another idea and would like to bounce it off you. Instead of subclassing AbstractTextField to create NumericField, I can just use TextField as is, but define a new binding prefix for the translate parameter which will allow the format pattern to be specified as the binding expression, like this:
<t:textfield t:id="latitude" translate="numberformat:0.00000" /> I will need to create a new BindingFactory to return a numeric translator that uses the specified format. What do you think? Will this work? Benny On Wed, Dec 23, 2009 at 11:32 AM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > Em Wed, 23 Dec 2009 14:01:03 -0200, Benny Law <benny.mk....@gmail.com> > escreveu: > > Hi Thiago, >> > > Hi! > > > should be displayed. Where I got lost is figuring out how to provide the >> custom translator from within NumericField. >> > > In this case, I think it would be easier to not use a translator and do the > conversion yourself. > > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, software architect and developer, Ars Machina Tecnologia da > Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
