On Sat, 04 Dec 2010 12:13:02 -0200, Paul Stanton <p...@mapshed.com.au>
wrote:
I also can't find any documentation regarding the config of Translators
... ?
The contribution for TranslatorSource defines the default translator. If
you want to use another one, just pass it to the translator parameter.
You'll probably use the prop binding. Something like this:
<t:textfield ... t:translator="prop:fancyTranslator" />
public Translator getFancyTranslator() {
return ...
}
If you use alternative translators a lot, you can create a binding for
that, avoiding the methods to provide them.
You can't use a Translator directly as the format parameter to the Output
component because it expects a java.text.Format instance. I prefer to do
the formatting in the page or component class instead of using this
component.
--
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: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
