Re: Reusable translated button
Re: Reusable translated button
- Subject: Re: Reusable translated button
- From: Chuck Hill <email@hidden>
- Date: Tue, 22 Aug 2006 13:09:25 -0700
On Aug 22, 2006, at 2:03 AM, Fabrice Pipart wrote:
Thanks to you both Timo and Chuck
You were right, I was in the wrong direction and it was far far
easier to use project wonder for that purpose (though I loved the
KVC thing with @localize)
The ERXSession and its ERXLocalizer was set up in 5min and works
just like I dreamed :-)
Since it seems that all my questions to the list end with a "it's
already available in Project Wonder" and that its a far better
implementation than mine, I have a question :
What documentation is available for Project Wonder? How can I have
an overview of what project wonder can do for me?
I am not sure really. Kieran had a Quick Start on his blog, not sure
if I can still find it. This is a complaint that people often have
about Wonder: there is not much in the way of documentation on how to
get started and how to use it and what is there. As is common with
Open Source things, the developers add what they need. And they need
code not docs. As a new Wonder user, you need docs more than code.
So, er, perhaps you can write some and add them to Wonder. :-)
I found the Javadoc (it seems that the Javadoc on sourceforge is a
bit outdated compared to the one in the latest bin or sources).
I found some information in text files when I downloaded the
sources...
But is there anything better?
I mean it's a bit complicated to look in hundreds of classes' names
in a Javadoc to guess which one could help you.
And most of the time I don't even have the idea that wonder could
help me.
So, is there a good way to learn what project wonder can do?
Not that I am aware of. This is probably the single reason that
Wonder is not more widely used.
Chuck
On Aug 21, 2006, at 7:18 PM, Timo Hoepfner wrote:
Am 21.08.2006 um 17:19 schrieb Fabrice Pipart:
I am trying to make a reusable component to have buttons translated.
The idea is to just provide a key to the button that will take
care to find the translation in the .strings
This looks like Chuck's "LocaleString" but for buttons.
You could use Project Wonder with it's ERXLocalizer for that. Then
you can bind to e.g.
session.localizer.your_key
and it will be translated automagically based on what you
specified in your
Resources/English.lproj/Localizable.strings
Resources/German.lproj/Localizable.strings
...
The equivalent to "LocaleString" is probably "ERXLocalizableString".
It has a lot more stuff in there like pluralization, localizable
templates, where dynamic values can be mixed with localized
strings, etc.
Timo
www.easyshadow.com
International Corporate Consulting
Palais de la Scala
1 avenue Henri Dunant
Suite 1155
MC - 98000 Monaco
Skype: fabrice.pipart
Tel. +377 97 98 21 04 (direct)
Fax. +377 97 70 88 07
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden