Re: Localizable.strings ?
Re: Localizable.strings ?
- Subject: Re: Localizable.strings ?
- From: Ramsey Gurley <email@hidden>
- Date: Thu, 02 Aug 2012 11:29:24 -0700
Create a rule model group file for all the rule files in your project and find your rules in that. Double clicking a rule will open the correct rule model and take you to the rule. And yeah, you still want to use localized string keys for the interface strings, but you would make your rule based on whatever logic you need.
Ramsey
On Aug 2, 2012, at 11:15 AM, Theodore Petrosky wrote:
>
> yea i understood that. I was thinking in the Localizable.strings file!!
>
> either way. I was also looking at the docs to included a separate d2wmodel file for these name mappings.
>
> I noticed in every d2w video that I have watched (you included) a lot of time went into finding rules to edit them. I am thinking of the number of times I watched you looking for a rule in the demo and you gave up. There has to be a better way to organize the rules.
>
> Is there any downside to using multiple d2wmodel files?
>
> Ted
>
>
> --- On Thu, 8/2/12, Ramsey Gurley <email@hidden> wrote:
>
>> From: Ramsey Gurley <email@hidden>
>> Subject: Re: Localizable.strings ?
>> To: "Theodore Petrosky" <email@hidden>
>> Cc: email@hidden
>> Date: Thursday, August 2, 2012, 11:57 AM
>> Of course you can :-) Just create
>> your own rule. RHS is displayNameForProperty.
>>
>> On Aug 2, 2012, at 8:45 AM, Theodore Petrosky wrote:
>>
>>> But can I target PropertyKey.textArea5 differently if
>> the page is different, i.e..
>>>
>>> "EditListUser.PropertyKey.textArea5" = "string 1";
>>> "CreateListUser.PropertyKey.textArea5" = "string 2";
>>>
>>> Can this be done? or am I barking up the wrong tree.
>>>
>>> Ted
>>>
>>>
>>> --- On Thu, 8/2/12, Ramsey Gurley <email@hidden>
>> wrote:
>>>
>>>> From: Ramsey Gurley <email@hidden>
>>>> Subject: Re: Localizable.strings ?
>>>> To: "Theodore Petrosky" <email@hidden>
>>>> Cc: email@hidden
>>>> Date: Thursday, August 2, 2012, 11:31 AM
>>>> Oh, and BTW
>>>>
>>>> "PropertyKey.myBigAttribute" = "My Big Attribute";
>>>>
>>>> There's actually another one Q added to the
>> validation
>>>> system "MyEntity.myBigAttribute" which makes more
>> sense, but
>>>> no one, as yet, has gone through and updated the
>> erd2w
>>>> assignment to use that key instead.
>>>>
>>>> Ramsey
>>>>
>>>> On Aug 2, 2012, at 8:27 AM, Ramsey Gurley wrote:
>>>>
>>>>> Dump your created keys. Just go to the ListUser
>> page,
>>>> then click the "Created Keys" link in your page.
>> That will
>>>> dump all the created localizable strings into your
>> eclipse
>>>> console.
>>>>>
>>>>> Ramsey
>>>>>
>>>>> On Aug 2, 2012, at 8:22 AM, Theodore Petrosky
>> wrote:
>>>>>
>>>>>> I am looking over Ramey's HelloD2W and
>>>> Localizable.strings.
>>>>>>
>>>>>> I understand targeting the Navigation area
>>>> with nav.something. I don't understand how to
>> target
>>>> the different areas. For instance, if I wanted to
>> target the
>>>> attribute myBigAttribute on the "List User" page.
>>>>>>
>>>>>> Or am I not understanding what I can do
>> with the
>>>> Localizable.string?
>>>>>>
>>>>>> Ted
>>>>>>
>> _______________________________________________
>>>>>> 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
_______________________________________________
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