Comments on: jsCron: Schedule code to run via simple JavaScript

By: aslakhellesoy

aslakhellesoy — Wed, 14 Jan 2009 18:05:49 +0000

If it was possible to add a field for seconds I might use this.

By: AndyStevens

AndyStevens — Tue, 13 Jan 2009 18:04:30 +0000

@jaysmith
I’ve not actually tried it myself, but according to O’Reilly’s “Adobe AIR for JavaScript Developers Pocket Guide” eval() is “restricted within the application sandbox … Prohibited after onload. After the parsing time, you cannot use eval() to transform strings (such as those imported via XHR) into JavaScript code. The exception from this rule is eval() used with a string parameter of type JSON – pure JSON strings can be transformed into actual objects, although JSON code that contains call back functions are not supported.”
There’s a bunch of similar restrictions, e.g. document.write(), setTimeout() with a string parameter, and so on.

By: jaysmith

jaysmith — Mon, 12 Jan 2009 14:57:01 +0000

I may have missed that one. eval() does not work in Adobe Air applications?

By: aNieto2k

aNieto2k — Mon, 12 Jan 2009 13:32:32 +0000

Thx Spocke,

I change it and now you can use this method.

By: Spocke

Spocke — Mon, 12 Jan 2009 12:02:07 +0000

Why use eval and eval style setInterval. These methods are both slow and non working in for example an Air environment. So it can be done without evil evals.

Something like this would have been nicer:
jsCron.set(“35 17 * * *”, function() {
alert(“Yo!”);
});