We're using something similar for a localization project of our own. The application pulls the configured language from the users preferences, the local system setting, or the application configuration (in that order) and based on that populates a Strings Value Object that's housed on our singleton application model. That same value object in itself is just a fancy proxy object that caches any strings that have been requested rather than retrieving from the XML every time a binding fires.
If you can get your hands on a copy of Actionscript 3 with Design Patterns, the Settings Framework example on page 71 is pretty much what you need, though I warn you that your compiler will throw a whole slewful of warnings if you try to bind to it directly. I'm told that using ObjectProxy instead of Proxy will fix this, but I haven't had the chance to try it out. Michael Krotscheck Senior Developer RESOURCE INTERACTIVE <http://www.resource.com/> www.resource.com <http://www.resource.com> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of aaron smith Sent: Sunday, September 23, 2007 10:22 PM To: [email protected] Subject: [flexcoders] localization options in flex 2 Quick question. I'm looking into localization for an app, and one of my concerns is that every piece of text has to be in the correct language for a region. en, fr, etc. But there is quite a bit of text. So instead of having a .properties files for all these different languages for every piece of text. Can I just localize the flex components and just load the corresponding text from a language XML file. So an english xml, french xml, etc. That way instead of having to access a resource bundle with a key/val pair for a specific piece of text, I can just assign the corresponding text from xml to the .text property or .label, etc? I guess I don't see why I would absolutely have to use ResourceBundle's except for localizing the flex components. Any thought?
