That sounds great Harbs, so I guess the question is more: do we need to support IE10 and below, because targeting official support for these browsers seems to hold Royale back?
If we did not do that, then we can avoid the 'just in case' support for them (legacy browser compatibility in classes like ObjectMap could be an explicit PAYG choice instead of default). It really hinges on what the baseline browser compatibility is/should be for Royale, and I think that might simply need a revisit/review given that time has passed and more will pass before 1.0. If IE10 and under holds us back a lot, and if it is unvalued by Royale users (idk whether it is or not, this is up for debate) then maybe it should not be part of the 'Basic' browser compatibility set any more... just a thought. On Sun, Feb 25, 2018 at 9:59 AM, Gabe Harbs <[email protected]> wrote: > There is a ObjectMap class which uses WeakMap or Map and falls back to > regular objects on platforms whether that is not supported. > http://royale.apache.org/asdoc/#!org.apache.royale.utils/ObjectMap < > http://royale.apache.org/asdoc/#!org.apache.royale.utils/ObjectMap> > > It should be a decent replacement for Dictionary (including weak > references). The only caveat is you need to use get() and set() instead of > bracket access. > > I just added documentation and cleaned it up a bit. > > What’s interesting about that class is I needed to do some weird things > with the methods to reassign them. They are not showing up in the ASDoc > very well… > > There might be a better way to declare the method (variable) proxies. Not > sure… > > HTH, > Harbs > > > On Feb 24, 2018, at 9:10 PM, Greg Dove <[email protected]> wrote: > > > > That might make porting some legacy Flex code a > > lot easier, for example because (iiuc) I think that means Dictionary with > > weak keys could be supported. [3] (and I know Harbs did something related > > to this in the past, maybe some sort of polyfill, can't recall exactly) > >
