Re: How to overridide DoubleTranslator as DoubleTranslator is not localized
I voted and really hope that it will be corrected. I repeat my question here once more if Howard misses it in the Jira: Is there a good reason not to let developers to override the default translators? - 99 Ulrich Stärk wrote: I'm having the same issue, see here: http://markmail.org/message/jtzc7doxqcbn7ac7 I'm working with a patched version of Tapestry, using a patch I provided here: https://issues.apache.org/jira/browse/TAPESTRY-2457 Another workaround could be to provide all of your fields that shouldn't use the default translators with your own one. You'll have to instantiate these custom translators on every page where you need them with the user's current locale. This is cumbersome but right now the only way I see. If you want to use the BeanEditForm with your own translators you'll have to overwrite the editors for the respective properties. See the Property Editor Overrides section here: http://tapestry.apache.org/tapestry5/tapestry-core/guide/beaneditform.html Maybe Howard will include my patch or fix this in some other way if enough people vote for the issue so you might consider voting for it. Uli 9902468 schrieb: Hi! How can one override the default double translator in Tapestry 5? I want to replace the default altogether, but have found only instructions how to contribute new ones. Why the add method in configurations doesn't replace the existing ones? Now it gives warning and doesn't override the default ones. And why the default double translator doesn't use numberformat and Tapestry's locale to output the number correctly? (And parse for that matter?) This is a flaw in otherwise nicely localized application, any thoughts? - 99 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/How-to-overridide-DoubleTranslator-as-DoubleTranslator-is-not-localized-tp18133977p18148964.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to overridide DoubleTranslator as DoubleTranslator is not localized
Hi! How can one override the default double translator in Tapestry 5? I want to replace the default altogether, but have found only instructions how to contribute new ones. Why the add method in configurations doesn't replace the existing ones? Now it gives warning and doesn't override the default ones. And why the default double translator doesn't use numberformat and Tapestry's locale to output the number correctly? (And parse for that matter?) This is a flaw in otherwise nicely localized application, any thoughts? - 99 -- View this message in context: http://www.nabble.com/How-to-overridide-DoubleTranslator-as-DoubleTranslator-is-not-localized-tp18133977p18133977.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to overridide DoubleTranslator as DoubleTranslator is not localized
I'm having the same issue, see here: http://markmail.org/message/jtzc7doxqcbn7ac7 I'm working with a patched version of Tapestry, using a patch I provided here: https://issues.apache.org/jira/browse/TAPESTRY-2457 Another workaround could be to provide all of your fields that shouldn't use the default translators with your own one. You'll have to instantiate these custom translators on every page where you need them with the user's current locale. This is cumbersome but right now the only way I see. If you want to use the BeanEditForm with your own translators you'll have to overwrite the editors for the respective properties. See the Property Editor Overrides section here: http://tapestry.apache.org/tapestry5/tapestry-core/guide/beaneditform.html Maybe Howard will include my patch or fix this in some other way if enough people vote for the issue so you might consider voting for it. Uli 9902468 schrieb: Hi! How can one override the default double translator in Tapestry 5? I want to replace the default altogether, but have found only instructions how to contribute new ones. Why the add method in configurations doesn't replace the existing ones? Now it gives warning and doesn't override the default ones. And why the default double translator doesn't use numberformat and Tapestry's locale to output the number correctly? (And parse for that matter?) This is a flaw in otherwise nicely localized application, any thoughts? - 99 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
