Hi,
It's done. You can see the result at
http://wiki.apache.org/tapestry/Tapestry5HowToAddMessageFormatBindingPrefix.
I've tested this on two of my sites and it works beautifully.
I've added support for multi-part keys so you can do stuff like
${format:gender-,prop:user.gender} which will get you the message
gender-male or gender-female depending on user.gender. This can, of
course, be combined with formatting if needed.
-Filip
On 2008-04-03 01:33, Filip S. Adamsen wrote:
I've been thinking about adding support for this to the
MessageFormatBindingPrefix found on this wiki page:
http://wiki.apache.org/tapestry/Tapestry5HowToAddMessageFormatBindingPrefix
If you take a look at it the code, MessageFormatBindingFactory in
particular, you'll see that making the message key itself a binding
wouldn't be too difficult. It should probably default to literal to
preserve current behaviour, though.
You can have a go at it yourself or wait a few days for me to do it.
-Filip
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
