I never liked ResourceBundle tag too but it was what I had with Flex. Here in a new application is also a new opportunity to do better but I will have to use what we have. I liked the way that Harbs mentioned it.
Carlos Rovira <[email protected]> escreveu no dia quarta, 1/07/2020 à(s) 09:55: > In Jewel you can check Validator.as > It implements resourceManager > through a bead: iLocalizedValuesImpl > > but I remember talking with Alex that was not a good idea, or maybe we can > improve it. But it's something to improve for the future. > > I never liked the ResourceBundle tag, and in fact never use it in real Apps > since we used translations from Java Spring. > But Royale UI Sets should have something built-in to deal with things like > form validator error messages, but not the way is done currently > where we "bake" language messages on it. > > Is something to think about it... > > > El mié., 1 jul. 2020 a las 8:32, Harbs (<[email protected]>) escribió: > > > [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 ? > > > > > > -- > Carlos Rovira > http://about.me/carlosrovira >
