Hi, just let you know that IE11 problem wasn't a JSON problem. It was that "atob" and "btoa" functions to decode/encode base64 are not available in IE11...another IE nightmare... I finaly added a Base64 class with static encode and decode functions to Core to solve this problem cross platform.
So final I was able to finish the example... Thanks Carlos El dom., 23 sept. 2018 a las 17:37, Carlos Rovira (<[email protected]>) escribió: > Hi Harbs, > > thanks! that solves the issue! That's magic! : ) > > I put this only in pom.xml in this example and in JewelExample, since I'll > use it as well. But I think I can't enable it in maven globally, or at > least don't know how. > I think as you that this should be enabled per case, although, it seems > that even we, that use mostly AMF instead JSON, will have to use it, so > maybe all people using royale, will end using this compiler arg...just what > I think will happen. > > About IE11, I'll go with it now, but seems that JSON.parse() has many > problems with many functions and people uses polyfill or other JSON > implementation to solve it. I'll try that way and I think if that works ok > and we want to support IE11 as we said, we'll need to add the polyfill to > Royale as we did with other things like Dialog. > > Thanks! > > > El dom., 23 sept. 2018 a las 11:49, Harbs (<[email protected]>) > escribió: > >> I’m not sure what the problem is with IE11, but the problem with the >> release version is minification renaming. >> >> I just committed a change to the example ant build script to include the >> “js-dynamic-access-unknown-members” option (new to 0.9.3). That fixes the >> renaming problem. >> >> You can do something similar for Maven and/or VS Code builds. >> >> I’m not suggesting that globally enabling this option (like I did) is the >> best way to go, but I have limited time today and I wanted to demonstrate >> how to use it. >> >> Good luck, >> Harbs >> > > -- > Carlos Rovira > http://about.me/carlosrovira > > -- Carlos Rovira http://about.me/carlosrovira
