Digital Workshop

Opus has a storage action that writes to cookies - actually it's HTML5 localStorage. This is persistent between sessions. Failing which there is a postwebdata action for server side storage.

If your contemplating mashing external JavaScript then you have IndexDB which has decent browser support or the FileWriter API which still has limited support.

http://caniuse.com/

Mack

Not sure if you sent us the anonymous email, but I'll answer the question here as it might help in general. I'm not building Android applications so am not delving too deeply into what works and what doesn't - but having taken a quick look at local storage for Android - it appears that it is possible but requires something call DOM storage to be enabled for the webview. As it appears to fail - I assume that it's not enabled?

I'd hazard a guess that this occurs at build time and therefore is not something that a user of Opus can include but would need to be added by DW (I might be very wrong).

Mack

Oh. Somebody sent it via our contact form on our website. As it was about storage in Android applications, I though it might be you.

Opus Pro 9.5 is the beta version and therefore only available to evolution members for testing at the moment. If you've subscribed but not had a link, send support an email.

Mack

It's an outside the box solution but publishing it as HTML5 and packaging it using Intel's XDK (latest) will enable localStorage by default.

Mack

We’ve released a silent update which includes a fix for cookies under Android so you should be able to do this from within Opus now.

If you want it before the official release then you can simply go to the updates page and download the existing update from there. We’ll officially announce v9.51 once any other items are in place but thought you could use it now. It also includes a build number from Android output which is required if you want to upload updated versions of your app to the Google marketplace.

Paul

You need to specify a whole number in the version field on settings.

However, a quick test on my Fire and cookies (localStorage) didn't appear to work anyway

</mack>

The latest build (in help about) should be 16651. Can you check that's the one you're running?

Nope. 16647. And that's from the download that just finished now.

</mack>

Mine was the EXE as well

Tried the MSI, Nov 9th Build and this now shows the build number in settings, publishes without error and read and write cookies worked on JB and ICS devices.

[edit] Dave's right. It will read and write under JB but a restart deletes the data.

</mack>

Obviously we screwed up somewhere with the installs.

I tried switching off the device with the cookies, and it works in 4.4 (KitKat), but not 4.2.

Apologies for the confusion with the uploaded versions. For the avoidance of doubt can everyone try the version here:

http://www.digitalworkshop.com/downloads/beta/opus_pro_9.exe

and confirm that the Android publishing and cookies work.

Thanks.

Paul

No, doesn't appear to work with ICS when the device is switched off.

v16655 - Nov 16th Build

mack

I had also been testing with Build 16647 (not 16655), and can not get write variable to cookie/read variable from cookie to work in an HTML5 pub.

Is the local storage to/from cookies only for Android, or will it also work for HTML5?

Working on an HTML5 project: so far, can't set a variable to true/false or 0/1, have it persist when going back and forth between 2 pages and work. When user clicks a button, want to set a (persistent) variable to true or 1, then when the user navigates to another page and returns back to the original page where the button is, either disable that button or hide it, since that button has already been used. This would be easier to do with a local storage than posting web data requiring an ASP or PHP server side page.

Doesn't appear that Build 16655 fixed this?

Hi Valero,

Thank you for your reply.

I installed 16655, and it works, for what I need it to do, in the HTML5 pub. In this pub, I am actually not looking for variable data to persist once the pub is closed. It only needs to persist from page to page while open and then start over again (on SCORM start page, added var = "") next time viewed.

But I can see the value of persistent data storage, especially in an Android pub.

I hope however that whatever changes/fixes are subsequently made, that the current storage ability I am using in 16655 for HTML 5 (write/read variable to cookie) will remain available.

Best Wishes,

Hi Stephen,

The actions in Opus called Write Variable to Cookie refers to the HTML function of local storage.

Opus uses local storage (as can be confirmed by using the development tools of any decent browser) and this storage does remain once the machine is turned off and then back on.

Whether this works is depended on the browser not the device or type of device and with the exception of Opera Mini, local storage is supported across the board -

http://caniuse.com/#feat=namevalue-storage

If you are setting a cookie in Opus and it is not there when you either reload the browser or restart the machine - then you need to check what might be deleting (or preventing the storage of) the data - such as using Private Browsing Mode; using browser cleaning options or other third party tools for clearing browser history.

The cookies work fine in IE, FF, Chrome & Opera on the desktop and FF, Chrome and Android Stock browser on all my Android devices when simply building for a HTML5 publication type. There is no reason to think they won't continue to work either - as local storage is a standard part of HTML5.

However, how HTML5 behaves inside an Android package depends on the version of Android a device is running and HTML5 things that work perfectly as just .htm files loaded directly into any browser - can and do fail when packaged as an .apk.

Hope that clears it up a little.

</mack>





</mack>