I'm pretty sure you can add your own setters/getters for each attribute and
language, i.e.:
public String value_en()
{
return (String) eo().valueForKey("value_en");
}
public void setValue_en(String inValue)
{
eo().takeValueForKey(inValue, "value_en");
}
-G
On Feb 18, 2012, at 8:49 AM, Kevin Hinkson wrote:
> Hi all,
>
> I have some EO attributes successfully localized and up to this point they
> have mostly been values that do not change much. However, I now will have
> some values in the db that may change often and I am wondering what the best
> practice is for how setters for localized attributes are handled?
>
> 1. Is just the correct localized value updated in the database by magically
> reading the current language settings?
> 2. How would I go about setting the _en, _fr and _es values for a key via the
> EO?
>
> PS: wasn't there a search field at the top of this mailing list at one point
> in time?
>
> — K.R.H.
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/george%40boxofficetickets.com
>
> This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
