"this has the advantage of allowing me to make localeStrings a typed class so I get type checking on the actual strings to prevent mistakes"
That's a very good idea ! I never liked the way that Flex deals with that and sometimes there are type check errors that I can only see at runtime. Can you give an example, how the value changed (language value) in the constant: LocaleManager.localeStrings.OK ? Harbs <[email protected]> escreveu no dia quarta, 1/07/2020 à(s) 07:32: > [ResourceBundle] has support, but I’m pretty sure that’s in mx. You can > probably use it even if you’re not using mx components (I think). > > I’ve always used my own home-grown method of loading locale strings and > construct them into an object which is read using keys. > > i.e. LocaleManager.localeStrings.OK > > Besides the fact that I hate “magic”, this has the advantage of allowing > me to make localeStrings a typed class so I get type checking on the actual > strings to prevent mistakes... > > HTH, > Harbs > > > On Jul 1, 2020, at 3:14 AM, Hugo Ferreira <[email protected]> > wrote: > > > > What's the recommended approach for localization in Royale ? > > An out of the box API that grabs a txt file with the key/values ? > >
