NW.js and Electron detection

[dy]

It would be nice to have a possibility to detect Node-Webkit, as well as Adobe ExtendScript. There’s a lack of such lib for these platforms.

[jdalton]

Do you have UA strings or properties in the environment handy that platform.js can use as inferences?

[dy]

I know that Node-Webkit has three possible sources of information about platform.
First is the same global.window.navigator object as in Chrome. It contains information about browser. Particularly,

userAgent : "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.19 (KHTML, like Gecko) Chrome/22.90.11.27 Safari/537.19"

Second is global.window.platform, that is "node-webkit".
And third is global.proccess, that contains some useful info about OS and environment:

…
arch: "ia32"
…
features: {…}
platform: "win32"
versions: {
    …
    node: "0.8.14"
    node-webkit: "0.3.6"
    …
}

Anyway, I think it is advisable you to look at complete set of these properties.

[dy]

As for ExtendScript, the most correct way to get complete information about environment is to get BridgeTalk global object:

log(BridgeTalk) ==> 
{
appSpecifier : "photoshop-55.064" //or "estoolkit-3.6"
appName : "photoshop" //or "estoolkit"
appVersion : 55.064
appLocale : 
appInfo : 
appInstance : 
appStatus : "PUMPING"
arguments : null
length : 0
arity : 0
name : "BridgeTalk"
}

So, useful properties there are every with app prefix: appName, appVersion, appSpecifier, …

[bnjmnt4n]

I also intend to add support for atom-shell while I'm at it.

[bnjmnt4n]

I don’t think I'll be adding ExtendScript support, since not many people use ExtendScript.

[lipis]

Maybe after 3 years.. it's about time to actually support this thing :)

[jdalton]

@lipis Create a PR :D

[bnjmnt4n]

@lipis I haven’t had much time to maintain platform.js last year, but I’ll try to close up the rest of the issues by the end of January. PRs would be great though :)