RC2 of node-webkit 0.5.0 released

[Roger]

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

Changes since 0.5.0rc
================

* console.log() works again. (#609)

* security fix to prevent window.parent frame access from iframe from different domain (#534)

* package.json can't be read when there is '..' in the command line argument for app path (#627)

New Features
==========
* Chromium upstream is updated to version 27.0.1430.0

* Printing support (#56): window.print() works now. The print preview
feature is not included yet. We plan to add it before 0.5.2 release.

* Specifying initial working path of file dialogs (#516): a new attribute
'nwWorkingDir' is added on the input element of file type. It can be used
to specify or override the initial path of the file dialog.

* Supports CMD-` to cycle windows on OSX (#432)

* Ignore iframe 'X-Frame-Options' for Node frames (#461): so you can
"basically create a mini-browser inside of node-webkit using iframes. Most
of the big sites on the web now refuse to be shown in a frame as a result
of that header"

Bug fixes
=======
* showDevTools() breaks events in new windows (#602).

There should be more bug fixed with this release, which we'll scrub and
update later.

[rads...@gmail.com]

The window.parent frame security fix breaks my app. The app contains an iframe that loads the Rdio Web Playback API. I'm forced to load the player through a separate web server because Rdio's API doesn't work with file:/// URLs. Before 0.5.0rc2, I was having the iframe set a reference to the player in the parent window, e.g. `window.parent.rdio_player`. Now that this fix is in place, I see two possible alternatives:

1. Control the player inside the iframe using frame.contentWindow.

Unfortunately this doesn't seem to work with the Rdio API, but I could be doing something wrong.

2. Communicate through the web server itself using dnode or AJAX.

This would work, but it adds another layer of boilerplate code.

Do you have any ideas on the simplest way to work around this new limitation?

[Roger]

Another way is to add your (trusted) domain to 'node-remote' field in the manifest. Does it fix for you?

https://github.com/rogerwang/node-webkit/wiki/Manifest-format

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.
 
 

[Chris Granger]

You can put a function in the frame's window object that lets you set the instance. e.g. frames[0].set_rdio = function(inst) { window.rdio_instance = inst; }

Cheers,
Chris.

[Andry Bray]

Hello, congrats for the new rc!

I'm new on this group but I'm following your project since some month ago.

I'd like to know if there is a way to fix the app crash with MacOS 10.6.x... (the main reason I need a fix it's because of new feat. for window.print() )

I'm trying to run the app but it's going always to crash and this is the report:

Process:         node-webkit [423]

Path:            /Users/admin/Downloads/MyApp.app/Contents/MacOS/node-webkit

Identifier:      com.intel.nw

Version:         27.0.1430.0 (1430.0)

Code Type:       X86 (Native)

Parent Process:  launchd [113]

Date/Time:       2013-04-17 12:10:06.690 +0200

OS Version:      Mac OS X 10.6.8 (10K549)

Report Version:  6

Interval Since Last Report:          5752827 sec

Crashes Since Last Report:           23

Per-App Interval Since Last Report:  4 sec

Per-App Crashes Since Last Report:   3

Anonymous UUID:                      6D47F142-7CF0-486E-9E06-A97916556819

Exception Type:  EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

Crashed Thread:  0  CrBrowserMain  Dispatch queue: com.apple.main-thread

Thread 0 Crashed:  CrBrowserMain  Dispatch queue: com.apple.main-thread

0   node-webkit Framework         0x6585ea4d uv__fs_event_close + 4717133

....

Any way to fix?

Thank you!

[Roger WANG]

Andry Bray <bur...@gmail.com> writes:

> Hello, congrats for the new rc!
> I'm new on this group but I'm following your project since some month ago.
>
> I'd like to know if there is a way to fix the app crash with MacOS
> 10.6.x... (the main reason I need a fix it's because of new feat. for
> window.print() )
> I'm trying to run the app but it's going always to crash and this is the
> report:

Hello Andry,

Thanks for your interest. It's a known problem:
https://github.com/rogerwang/node-webkit/issues/97

The fix is to build node-webkit in MacOS 10.6, which I don't have. The
only Mac I got has 10.8 installed. I can look into how to build and test
a 10.6 binary in 10.8 environment. Help on how to do this are welcome.

--
Roger WANG Intel Open Source Technology Center

[Andry Bray]

Thank you for your answer.

I'm not so expert with building process but I found this post:

https://groups.google.com/forum/?fromgroups=#!topic/firebreath-dev/ttGX2-LEj4g

it seems there is a way to change the default sdk with -D CMAKE_OSX_SYSROOT="/Developer/SDKs/MacOSX10.6.sdk" 
Maybe I'm writing stupid things =) and if it's like that, I'm sorry!

Anyway, I have the 10.6 version of MacOS. Maybe I could try to do it. Is it enough to follow these steps?

https://github.com/rogerwang/node-webkit/wiki/Building-node-webkit

PS:

As toommor says here https://github.com/rogerwang/node-webkit/issues/645 :

 Unfortunately I don't think it's possible, the newer versions of Chromium don't run on 10.6 - if you are on that version you'll find your Chrome has stopped updating months ago.

Is that true?

Thank you

[chjul...@gmail.com]

Hi, I have problems running node-webkit 0.5.0 under Linux

OpenSuSe 12.3

[8206:0418/222601:ERROR:zygote_host_impl_linux.cc(146)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[8206:0418/222601:INFO:gpu_info_collector_linux.cc(78)] NVCtrl extension does not exist.
[8227:0418/222601:ERROR:renderer_main.cc(203)] Running without renderer sandbox

Ubuntu:

[3657:0418/143405:ERROR:zygote_host_impl_linux.cc(146)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

[3657:0418/143405:INFO:gpu_info_collector_linux.cc(78)] NVCtrl extension does not exist.

[3677:0418/143405:ERROR:renderer_main.cc(179)] Running without renderer sandbox

Can someone give me a hit, what I am doing wrong?

--Alexey

[Chris Granger]

Those are benign errors, they shouldn't effect your app at all.

Cheers,
Chris.

[Donghao Ma]

please try this: ./nw --enable-logging --v=1

在 2013年4月19日星期五UTC+8下午1时32分03秒，chjul...@gmail.com写道：

[chjul...@gmail.com]

[9528:0419/101341:ERROR:zygote_host_impl_linux.cc(146)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[9530:0419/101341:VERBOSE1:zygote_main_linux.cc(469)] ZygoteMain: fork delegate is NULL
[9528:0419/101341:INFO:gpu_info_collector_linux.cc(78)] NVCtrl extension does not exist.
[9549:0419/101341:ERROR:renderer_main.cc(203)] Running without renderer sandbox
[9549:0419/101341:VERBOSE1:transport_dib_linux.cc(50)] Created SysV shared memory region 17137725
[9528:0419/101341:VERBOSE1:resource_loader.cc(336)] OnResponseStarted: nw:blank
[9528:0419/101341:VERBOSE1:resource_loader.cc(376)] OnReadCompleted: "nw:blank" bytes_read = 1082
[9528:0419/101341:VERBOSE1:resource_loader.cc(376)] OnReadCompleted: "nw:blank" bytes_read = 0
[9528:0419/101341:VERBOSE1:resource_loader.cc(627)] ResponseCompleted: nw:blank
[9549:0419/101341:VERBOSE1:shell_content_renderer_client.cc(181)] WillSetSecurityToken: nw:blank
[9549:0419/101341:VERBOSE1:shell_content_renderer_client.cc(181)] WillSetSecurityToken: nw:blank
[9549:0419/101341:VERBOSE1:shell_content_renderer_client.cc(158)] DidCreateScriptContext: nw:blank
[9528:0419/101341:VERBOSE1:x11_util.cc(419)] Got shared memory segment 17170494
[9528:0419/101341:VERBOSE1:x11_util.cc(433)] X got shared memory segment 17170494
[9528:0419/101341:VERBOSE1:x11_util.cc(445)] X attached to shared memory segment 17170494
[9528:0419/101341:VERBOSE1:x11_util.cc(1134)] X attached to shared memory segment 17137725

[rads...@gmail.com]

On Tuesday, April 16, 2013 7:39:01 PM UTC-7, Chris Granger wrote:

You can put a function in the frame's window object that lets you set the instance. e.g. frames[0].set_rdio = function(inst) { window.rdio_instance = inst; }

This worked perfectly. Thanks!