Digital Workshop

I've been developing my project as an One page export with hash tag. Because of the size I wanted to export it with Multiple pages.

What happens: book variables are remembered unless it is an array variable. When moving from page to page array variable is always cleared when entering a page.
Can you advice me how I should store an array between pages using Opus? May be to use some way of the Web Storage (http://www.w3.org/TR/2009/WD-webstorage-20091222/)?

Ota

I'd hazard a guess that this is a bug and contact DW.

However;

localStorage requires the data to be in string format and therefore you'll need to convert your data back and forth. Opus already has an action for session storage, so you simply need to convert the array to a string and use the action to save and then load on the next page and convert back to an array.

If you're looking for a simple method look at using Array.join and String.split to convert the data - if your data is more advanced you can use window.JSON functions from within Opus.

Mack

Thanks you saved me time with string information. I'll send it to support.
I have been using an array to a string for storing a cookies from Opus so I can use it for an array between pages.

Algorithm for keeping a pair of information in a string (values separated by coma) I've found on the Internet. It can be useful for others:

Code:

function getArray(str, type)//str e.g.: "Page_1_,completed,Page_2_,visited,Page_3_,completed"
{
    var pages = [];
    var status = [];
    for (var i=0;i<str.length;i++)
    {
        if ((i+2)%2==0) {
            pages.push(str[i]);
        }
        else {
            status.push(str[i]);
        }
    }
    if(type == "pages")
    {
        console.log(pages);
        return pages;
    }
    else
    {
        console.log(status);
        return status;
    }
}

in Opus I can fill an array with variables and then use it in text fields:

Code:

var_COMPLETED_PAGES = window.getArray(strArr, "status")
var_URL_PAGES = window.getArray(strArr, "pages")

Thanks again Mack. JSON works within Opus and is super easy to use.


Ota

Hi All,

I started a new Windows EXE publication and I need to pull a JSON from online into multiple variables. It is my understanding I can do this in Opus V9 via OpusScript, can someone describe the process for doing this? Previously I manually parsed the returned HTML and split out the JSON via OpusScript, but there must be an easier way.

I am using the Post Web Data action to get the HTML and JSON into a variable in Opus to manipulate it from there, I believe this is not the correct way of doing it. Any advice is greatly welcome.

Thanks, Luke

No, I think you misunderstand.

JSON is a JavaScript function and therefore available to the browser and thus HTML5 Opus publications.

Such functions can be accessed within OpusScript by accessing the window object and therefore the results made available to objects of the _DWPub. In the example above, this principle is used to assign the results of a JavaScript function (JSON) to a property of the Opus _DWPub Object (AKA a variable).

For Windows EXE Applications, a JSON string could be parsed using PHP on a server and echoed to the Opus Application as an object for use.

</mack>

Thank you Mack,

Ah ok, that's what I thought the issue might be. Ok I will dig up my old JSON parser I created a while back and see if I can get it to work. I wrote the code in 2011 so I cannot remember if it is dynamic or if I built it for a specific JSON I was expecting, I'll check and post the OpusScript here if dynamic.

When you say parse it in PHP and give it to Opus as an object, is that it being pulled into Opus via the Post Web Data? Some more information on this would be greatly appreciated.

Thanks, Luke

Yes, using POSTWEBDATA.

A simple PHP example:



Then you just set the receive tab as multiple fields and match the parameters in the echo string to your variables.

</mack>

Fantastic, that's much easier. I really did go to town on parsing a JSON via OpusScript.

Thanks as always Mack, I appreciate your quick response.