Re: [Wonder-disc] Localization issue
Re: [Wonder-disc] Localization issue
- Subject: Re: [Wonder-disc] Localization issue
- From: Theodore Petrosky <email@hidden>
- Date: Tue, 28 Jan 2014 13:26:17 -0500
I didn't answer this because I wasn't sure if I created this component or stole it from somewhere.
I set my boolean to my component that creates its 'list' and assigns the true and false to propertyKeys with rules:
100 : propertyKey = 'isActive' => emptyBooleanPopup = "Both Active and Inactive" [com.webobjects.directtoweb.Assignment]
100 : propertyKey = 'isActive' => popupBooleanFalseValue = "Only Inactive" [com.webobjects.directtoweb.Assignment]
100 : propertyKey = 'isActive' => popupBooleanTrueValue = "Only Active" [com.webobjects.directtoweb.Assignment]
so the popup shows what I want.
Is this what you are looking for?
I thought this was a 'normal' component and I don't remember writing it. If you want it, let me know.
Ted
On Jan 28, 2014, at 11:24 AM, Fabian Peters <email@hidden> wrote:
> Even so, when ^yesName returns null (as I guess it should in your case), it should simply use valueWhenEmpty = "Yes" – so you should be able to localize "Yes" = "Oui"?
>
> Fabian
>
> Am 28.01.2014 um 15:59 schrieb email@hidden:
>
>> Thanks,
>>
>> I can't look at the component right now, but IIRC, the choicesNames is used if there are more than one choice.
>> Otherwise (which is the case when you want to use a checkbox and provide a single choice), it no longer uses the first (and only) element in choicesNames, but rather ^yesName.
>>
>> I'll check again ASAP.
>>
>> JPM
>>
>> ----- Mail original -----
>> À: "WOnder-disc" <email@hidden>
>> Cc: "Jean Pierre Malrieu" <email@hidden>
>> Envoyé: Mardi 28 Janvier 2014 12:59:02
>> Objet: Re: [Wonder-disc] Localization issue
>>
>> Hi Jean Pierre,
>>
>> Since nobody seems to have replied: You should be able to use ERD2WCustomEditBoolean and localize the values you pass in via the "choicesNames" key, e.g. ("Yes", "No").
>>
>> Fabian
>>
>> Am 25.01.2014 um 12:22 schrieb Jean Pierre Malrieu <email@hidden>:
>>
>>> I have faced a small problem with D2W and localization
>>>
>>> The ERXBooleanSelector component has a yesString binding, and yet, when displaying a checkbox, it uses it's parent's component yesName variable:
>>>
>>> YesName: ERXLocalizedString {
>>> value = ^yesName;
>>> valueWhenEmpty = "Yes";
>>> }
>>>
>>> Thus ERD2WCustomEditBoolean does not localize properly... I wonder if this can be fixed by modifying ERXBooleanSelector wod to
>>>
>>> YesName: ERXLocalizedString {
>>> value = yesString;
>>> valueWhenEmpty = "Yes";
>>> }
>>>
>>> as this might break some person's code implementing yesName in a parent component (very unlikely given the existing yesString binding)...
>>>
>>>
>>> JPM
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>>> Learn Why More Businesses Are Choosing CenturyLink Cloud For
>>> Critical Workloads, Development Environments & Everything In Between.
>>> Get a Quote or Start a Free Trial Today.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Wonder-disc mailing list
>>> email@hidden
>>> https://lists.sourceforge.net/lists/listinfo/wonder-disc
>>
>
>
> _______________________________________________
> 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
_______________________________________________
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