I'd like to see either or both of the techniques. I thought that it wasn't possible to override Tapestry's built-in translators. (See TAP-725, "You cannot define two different translators for a single field type.") When I tried to add custom translators for String and BigDecimal types, either my translator got ignored or it got applied to all properties of that type. I'd love to hear that I'm missing something.
On Sun, Dec 27, 2009 at 9:02 AM, Ville Virtanen <ville.virta...@cerion.fi>wrote: > > Hi! > > If you get this working please share the results. This is something I never > thought when adding our number format handling. (Which is based on custom > translators. I'm happy to share the current solution if you are > interested?) > > - Ville > > > Benny Law wrote: > > > > On Thu, Dec 24, 2009 at 5:41 AM, Thiago H. de Paula Figueiredo < > > thiag...@gmail.com> wrote: > > > >> > >> This is very clever! I guess it'll work. :) Just pay attention that the > >> parameter received by the translate is a FieldTranslator, not a > >> Translator > >> itself. > >> > >> Thanks Thiago. I already found out the hard way, but it's basically > >> working > > now :) The last thing I still need to figure out is the purpose of > > FieldTranslator (I read the doc but still didn't fully get it) and how I > > can > > allow the error messages to be overridden in the message catalogue on a > > per > > field basis in the standard manner. I guess I need to use some other > > service > > to do that. Any hint will be appreciated :) > > > > > > -- > View this message in context: > http://old.nabble.com/Number-Formatting-in-TextField-%28T5%29-tp26398708p26934138.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
