Re: SharedObject should be in Storage lib

2020-01-30 Thread Carlos Rovira
Hi Alex, I'm a huge fan of AMF and I think is worth it to use with the current SharedObject implementation done by Greg that already support AMF. Of course others could use other options. As you say, we need to give options. El jue., 30 ene. 2020 a las 21:16, Alex Harui () escribió: >

Re: SharedObject should be in Storage lib

2020-01-30 Thread Alex Harui
SharedObjectJSON sounds useful and a good alternative short of AMF. I'm sure you're not surprised to hear me say that we should give users choices depending on their needs. If they only need to store simple values, LocalStorage should work. I think we do have Strong-Type to JSON and back

Re: SharedObject should be in Storage lib

2020-01-30 Thread Greg Dove
I think the browser can store objects already? Perhaps there is some way to do that, but I could not find anything for localStorage: ' The keys and the values are *always strings* (note that, as with objects, integer keys will be automatically converted to strings). ' The LSO version is an

Re: SharedObject should be in Storage lib

2020-01-30 Thread Alex Harui
Hi Carlos, I probably don't understand your use case. I would not recommend to new projects to use AMF to store data locally. I think the browser can store objects already? And I would think the difficulty of re-coding SharedObject.setProperty to LocalStorage.setItem would be worth the

Re: SharedObject should be in Storage lib

2020-01-30 Thread Carlos Rovira
Hi Alex, I tried this and reverted the commit since it has more things to be considered. LSO can be considered part of the AMF set of code, and depends on AMF classes that are currently in MXRoyale, for that reason Greg created there and not in Storage. These classes will need to be refactored

Re: SharedObject should be in Storage lib

2020-01-30 Thread Alex Harui
I don't know if it would be more "general" since it would be Flash-specific, but re-use of code from Storage is always a great goal. The MXRoyale components re-use quite a bit of code from Basic. Taking a quick look at the ASDoc, SharedObject offers both Local and Remote flavors and a

Re: SharedObject should be in Storage lib

2020-01-30 Thread Harbs
Possibly a MX version with Flash APIs should use a more general version from Storage? > On Jan 30, 2020, at 5:45 PM, Alex Harui wrote: > > I don't know LSO or the Storage SWC that well, but there is some sort of > LocalStorageProvider.as file already in Storage. > > IMO, if you are planning

Re: SharedObject should be in Storage lib

2020-01-30 Thread Alex Harui
I don't know LSO or the Storage SWC that well, but there is some sort of LocalStorageProvider.as file already in Storage. IMO, if you are planning to 100% emulate the Flash LSO, that should go in MXRoyale. A more platform-independent API for local storage should go in Storage. I don't know

SharedObject should be in Storage lib

2020-01-30 Thread Carlos Rovira
Hi, I was searching for some Flex counter part to the LSO classes in MXRoyale but didn't find anything. So if nobody opposite I'll move to the Storage library that seems its natural place. Thanks -- Carlos Rovira http://about.me/carlosrovira