(2 replies, posted in Saitek Module General Discussion)

Great news!!!

Did you need any tricks in order to make them work ?

Cool, thank you for the tip!


(2 replies, posted in Saitek Module General Discussion)


Sorry for the late answer.
Indeed the code should be optimizable. Will check.


Indeed, working with cookies is a real pain with JS.
Here is a code which should help you:

function cookieMan(key, value, options) {

    // key and at least value given, set cookie...
    if (arguments.length > 1 && String(value) !== "[object Object]") {
        options = options || {};

        if (value === null || value === undefined) {
            options.expires = -1;

        if (typeof options.expires === 'number') {
            var days = options.expires, t = options.expires = new Date();
            t.setDate(t.getDate() + days);

        value = String(value);

        return (document.cookie = [
            encodeURIComponent(key), '=',
            options.raw ? value : encodeURIComponent(value),
            options.expires ? '; expires=' + options.expires.toUTCString() : '', // use expires attribute, max-age is not supported by IE
            options.path ? '; path=' + options.path : '',
            options.domain ? '; domain=' + options.domain : '',
            options.secure ? '; secure' : ''

    // key and possibly options given, get cookie...
    options = value || {};
    var result, decode = options.raw ? function (s) { return s; } : decodeURIComponent;
    return (result = new RegExp('(?:^|; )' + encodeURIComponent(key) + '=([^;]*)').exec(document.cookie)) ? decode(result[1]) : null;

Now you can set your cookie using:

cookieMan("myCookie", "myValue",  { path: '/' });

and read your cookie using:

var value = cookieMan("myCookie");

Untested but should work. You can also pass some options:

raw: true maining that the value will not be encoded
expires: the expiration date
path: from where the cookie will be applied
domain: the scope of the cookie
secure: whether the cookie need secure access

Indeed, ralf is right.

WebApp.Net has been design for WebKit browsers (but works in Firefox too).
There is actually no plan to support other browsers since the projet is not in so active state.


Can you post a screenshot of what that gives?
Also what browser is in 9700?


I wrote things with WebApp.Net evolution in mind but there are some radicaal changes which could make things hard to modify smile

Hi Richard,

This is somthing I've done writing my book, but never found time to update WebApp.Net to take advantage of it.

If you check me github page you'll see that I started to work on a brand new version of the framework but it is in very very slow dev.

Any example?

Not yet, really wonder why I have this issue. A10 doesn't seem so stable... sad

Hi Algerad3,

Is this a question for me?

Hi icepick,

you cannot link to webpage and keep the sliding effect.
I can't open your sample, can you give me an example of what you want to achieve?



(17 replies, posted in WebApp.Net General Discussion)


(17 replies, posted in WebApp.Net General Discussion)


(17 replies, posted in WebApp.Net General Discussion)

I know icepick, I'm sorry about that sad I'll do my best


(17 replies, posted in WebApp.Net General Discussion)

I think there is a tabs example in the old source of the demo that you can find somewhere on the forum.

If not let me know.


(4 replies, posted in Saitek Module General Discussion)

You can post tutos in russian here is you want but the english version is required too smile


(6 replies, posted in WebApp.Net General Discussion)

Wow, what can I say? smile thanks for the kind message!


(1 replies, posted in Gamalto)

Hi Guys,

As soon as we have something fully working and stable, I'll do an app to easily install everything.