Great ! That is one the features we cannot afford to miss...
Nicolas Granon > -----Message d'origine----- > De : Alex Harui [mailto:aha...@adobe.com.INVALID] > Envoyé : mardi 7 novembre 2017 18:24 > À : dev@royale.apache.org > Objet : Resources (I18N, globalization, localization) > > Hi, > > I just pushed a simple way of handling different locales in a Royale > app. > I purposefully did not call it ResourceManager for now since I don't > think it will be 100% compatible. I just wanted to get something out > there to get a discussion going. > > It looks like there is PAYG features for what was called resources in > Flex. In this implementation, you have to manual embed the .properties > files with a particular naming scheme, then the implementation will > lazily process the .properties files and pull the right string given a > single locale. It is more code to have, for example fall-through to > another locale's bundle if the current locale's bundle did not contain > a value for a key. And even more code to inject bundles at runtime. > > After I refactor the compiler, and any discussion on these > implementations settle down, we can look at having the compiler > automate whatever set of steps we settle on. For example, the Royale > compiler doesn't handle @resource in MXML. Is anybody using > @resource?The compiler currently doesn't handle resource bundles. And > we have to come up with a scheme for knowing which bundles to bundle if > the bundles are declared in SWCs. > > Also, IMO, it should be a different set of beads that determine which > locale should be primary at runtime. > > Thoughts? > -Alex
