On Fri, 24 Dec 2010 02:19:58 -0200, Paul Stanton <p...@mapshed.com.au>
wrote:
If no one can tell me what existing tapestry concept I'm missing I may
spend some time seeing if I can write some code to get this going.
Why don't you create a simple component that receives a Translator and the
value to be output value? Tapestry 5 made creating componets very easy, so
you don't need to be restrained to the ones provided by the framework.
I see the role of formatters and translators intricately linked -
otherwise there is certain code repetition and therefore maintenance
issues. Also, constantly defining getter methods in components to make
global formatters available is hardly a good approach, and no better
than extending a 'BaseComponent' to access these properties.
This could be solved with the old style "service" binding prefix which
is also gone from the implementation.
Just create your own binding here.
--
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
