This is working out nicely for me (the eval trick, and the fact that
ResourceManager.getString can take arguments).
The one case where I can't push a direct ResourceManager call all the
way into a binding expression is when labelFunctions or
dataTipFunctions are required.
In that case, assuming I
AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re: internationalization @ switching runtime
This is working out nicely for me (the eval trick, and the fact that
ResourceManager.getString can take arguments).
The one case where I can't push a direct ResourceManager call all the
way
: internationalization @ switching runtime
This is working out nicely for me (the eval trick, and the fact that
ResourceManager.getString can take arguments).
The one case where I can't push a direct ResourceManager call all the
way into a binding expression is when labelFunctions
Of Richard Rodseth
Sent: Friday, June 27, 2008 1:19 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re: internationalization @ switching runtime
Actually, they're mostly charts.
And this is somewhat theoretical, since I'm just trying to be
runtime-switch-ready - it's not a requirement
That's very clever.
Gordon's suggestion of adding [Bindable] metadata to the buildTitle()
method and overriding resourcesChanged() works nicely, and I could
imagine caching some strings in the override, but adding the override
in numerous components is a bit of a nuisance, so your idea is quite
5 matches
Mail list logo
