node-webkit v0.7.4 released

[Roger]

https://s3.amazonaws.com/node-webkit/v0.7.4/node-webkit-v0.7.4-osx-ia32.zip
https://s3.amazonaws.com/node-webkit/v0.7.4/node-webkit-v0.7.4-win-ia32.zip
https://s3.amazonaws.com/node-webkit/v0.7.4/node-webkit-v0.7.4-linux-ia32.tar.gz
https://s3.amazonaws.com/node-webkit/v0.7.4/node-webkit-v0.7.4-linux-x64.tar.gz

Changes since v0.7.3:

* support HTML5 color chooser (#583)
* support filesys api for app protocol
* support document.cookie for app protocol
* Change: App.dataPath should be a string rather than an array (#1112)
* Security Fix: prevent constructing FileList and File in nwdisable
frame (#1120)
* Fix: support command line argument '--ignore-certificate-errors'
so nw could work with custom certificate (#904)
* Fix: crash on accessing object in new instance (#1095)
* Fix: Ssl certificate errors should report error immediately, not
time out (#1103)
* Fix: child_process.spawn in detached mode does not detach on Mac and
Linux (#1096)

Cheers

Roger

[Anthony Ettinger]

I'm just curious. why do you have to "support" things that are already in the browser by default?

Roger

--
You received this message because you are subscribed to the Google Groups "node-webkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-webkit...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Anthony Ettinger
http://about.me/anthony.ettinger
ant...@ettinger.name
+1 (831) 406-1123

[Roger]

Anthony Ettinger <etti...@gmail.com> writes:

> I'm just curious. why do you have to "support" things that are already in
> the browser by default?

node-webkit is based on Content layer of the chromium project, and the
Chrome browser is also based on it [1]. The content layer contains the most
part of the Chromium project. Some HTML5 features requires support from
the upper part above the Content layer, e.g. printing, geolocation,
getUserMedia, etc.

We copied some of the upper part components from the Chrome browser to
node-webkit, including printing, getUserMedia so they can be
supported. But unfortunately some still don't e.g. geolocation.

Fortunately Chromium upstream is moving the upper part components to the
Content layer, or splitting them from the Chrome browser part[2]. It will
save our effort to support more features in the browser.


Roger

[1] http://www.chromium.org/developers/content-module
[2] http://www.chromium.org/developers/design-documents/browser-components

[Karan Kapoor]

Hi Roger

So is there maybe an approximate date by when all these excellent features will also be included. I'm really excited about using geolocation with node webkit.

Thanks and regards

Karan Kapoor

[pabl...@gmail.com]

Hello Roger.

Any news on HTML5 Geolocation? It is the main drawback for our use cases right now.