NW.js v0.13.0-alpha4 is available

[Roger Wang]

(NOTE: This version is a snapshot of the next major version 0.13 which 
is under active development. For now it’s not compatible with some of 
the APIs in 0.12, as we are refactoring them with a new technology 
from upstream. In the final release of 0.13, it will be compatible 
with all features in 0.12. It’s recommended for you to try this 
release and give your valuable feedback.) 

Hello, 

We are pleased to announce NW.js 0.13.0-alpha4. In this version 
Chromium is updated to version 45 and Node.js is updated to v4.1.2. 

We've also rewrite our test framework, integrate it into buildbot and start migrating cases.

Starting from 0.13.0-alpha0 we've been supporting Chrome Apps and many 
chrome.* APIs. For more information about it, see the previous 
announcement: https://groups.google.com/d/msg/nwjs-general/IqfH1RXNGlw/2PgeRGHO-B4J 

Download 
======== 
http://dl.nwjs.io/v0.13.0-alpha4/nwjs-v0.13.0-alpha4-win-x64.zip 
http://dl.nwjs.io/v0.13.0-alpha4/nwjs-v0.13.0-alpha4-osx-x64.zip 
http://dl.nwjs.io/v0.13.0-alpha4/nwjs-v0.13.0-alpha4-linux-x64.tar.gz 

SDK build: 
http://dl.nwjs.io/v0.13.0-alpha4/nwjs-sdk-v0.13.0-alpha4-win-x64.zip 
http://dl.nwjs.io/v0.13.0-alpha4/nwjs-sdk-v0.13.0-alpha4-osx-x64.zip 
http://dl.nwjs.io/v0.13.0-alpha4/nwjs-sdk-v0.13.0-alpha4-linux-x64.tar.gz 

NaCl build and other platforms: http://dl.nwjs.io/v0.13.0-alpha4/ 

There are 3 builds for each platform - normal build, sdk build and 
Nacl build. Normal build doesn't have devtools, only SDK build does. 
lt can be opened by pressing F12 (Cmd-Alt-I on OSX). SDK package will 
also have more development tools to be exposed in the following 
releases, as well as the NaCl support. 

Our build infrastructure enables live binary build from git tip so you 
can access to the latest binary for this branch from 
http://dl.nwjs.io/live-build/nw13/ 

Known issues 
========== 
- [WIN] menubar not shown when DWN is disabled 

[Roger Wang]

PS: The Mac message loop integration is rewritten to fix blocking issue in previous alpha releases.

Roger

[VoidVolker]

Thanks Roger! Is there any full list of changes? 

[Roger Wang]

Hi VoidVolker,

There is no change on the visible API level. Most of the time is spent on improving the build infrastructure, test framework and the rebase. Previously we discussed here why the rebase in this version takes longer time than expected -- to resolve the conflict between openssl (in Node) and boringssl, which Chromium now uses exclusively. The new implementation of OSX message loop integration is exciting because hopefully it will fix issues reported by users but cannot be reproduced here.

We'll publish a spreadsheet listing all the APIs and the status of migration to nw13. Hopefully we'll port them all and enter beta in Nov. In the meantime we'll keep updated with Chromium and Node.js upstream. The next alpha version should be with Chromium 46 and Node v5.x (all uses v8 version 4.6). I'm also developing a feature of signing application files, so NW.js can be built with your key and refuse to load any unsigned code if your application is modified after redistribution.

Thanks and regards,

Roger

[Jimmie W]

Hi，Roger，

       I got this error when run nw in nwjs-nacl-v0.13.0-alpha4-linux-x64 on Linux Mint 17.1 x86_64 , which is downloaded from http://dl.nwjs.io/v0.13.0-alpha4/nwjs-nacl-v0.13.0-alpha4-linux-x64.tar.gz .

nwjs-nacl-v0.13.0-alpha4-linux-x64 $ ./nw 

[1026/112557:INFO:nw_package.cc(175)] ./nw

LaunchProcess: failed to execvp:

[1:1:1026/112557:FATAL:renderer_main.cc(174)] Failed to load node library (error: libnode.so: cannot open shared object file: No such file or directory)

         AfterI add LD_LIBRARY_PATH, same error happeed.

nwjs-nacl-v0.13.0-alpha4-linux-x64 $ LD_LIBRARY_PATH=./lib ./nw

[1026/113219:INFO:nw_package.cc(175)] ./nw

LaunchProcess: failed to execvp:

[1:1:1026/113220:FATAL:renderer_main.cc(174)] Failed to load node library (error: libnode.so: cannot open shared object file: No such file or directory)

Jimmie

在 2015年10月25日星期日 UTC+8上午7:12:23，Roger Wang写道：

[Roger Wang]

It looks like the issue of file permissions, could you change the owner to yourself or change the permission? I'll fix this in the next release.

Roger

[VoidVolker]

 I'm also developing a feature of signing application files, so NW.js can be built with your key and refuse to load any unsigned code if your application is modified after redistribution.

I'm already done this under linux for windows files - it very simple. Most problem is OSX: to sign files or DMG image need to be registered OSX developer and it can be done only in OSX. (maybe there exist solution for linux - I don't find it).

I use ossligncode and next script:

winsign.sh

#!/bin/bash

target=${1}
# result="./files/${1}"
cert="./cert/cert.spc"
key="./cert/private.key"
pass="roof"
rnd=$RANDOM$RANDOM$RANDOM
src="${target}_${rnd}"
mv $target $src
../tools/osslsigncode/osslsigncode sign -certs $cert -key $key -pass $pass -in $src -out $target
rm -f $src

# Usage: osslsigncode


#     [ --version | -v ]


#     [ sign ]
#         ( -certs <certfile> -key <keyfile> | -pkcs12 <pkcs12file> )
#         [ -pass <password> ] [ -askpass ][ -readpass <file> ]
#         [ -ac <crosscertfile> ]
#         [ -h {md5,sha1,sha2(56),sha384,sha512} ]
#         [ -n <desc> ] [ -i <url> ] [ -jp <level> ] [ -comm ]
#         [ -ph ]
#         [ -t <timestampurl> [ -t ... ] [ -p <proxy> ]]
#         [ -ts <timestampurl> [ -ts ... ] [ -p <proxy> ]]
#         [ -nest ]


#         MSI specific:
#         [ -add-msi-dse ]


#         [ -in ] <infile> [-out ] <outfile>


#     extract-signature [ -in ] <infile> [ -out ] <outfile>


#     remove-signature [ -in ] <infile> [ -out ] <outfile>


#     verify [ -in ] <infile>
#         [ -require-leaf-hash {md5,sha1,sha2(56),sha384,sha512}:XXXXXXXXXXXX... ]

It works for *.exe and *.dll files very well.

[Jimmie W]

The owner of dir nwjs-nacl-v0.13.0-alpha4-linux-x64 and the files in it both are my username. 

And after I executed 'chown -R $USER.$USER nwjs-nacl-v0.13.0-alpha4-linux-x64' and chmod -R 777 ... ，the error still happened.

Jimmie

在 2015年10月26日星期一 UTC+8下午12:26:28，Roger Wang写道：

[mikef...@gmail.com]

Roger,

Thank you (and all of the contributors) as always for your hard work on this project - it is fantastic.

A huge +1 on the idea of signing application files and running them only with a particular build of NW.js.

Cheers!

Mike

[potte...@gmail.com]

I'm having the same problem running on 64-bit Linux Mint.

Any ideas?

me@hostname /opt/nwjs-v0.13.0-alpha5-linux-x64 $ ll
total 14656
drwx------  4 me me    4096 Nov 14 00:06 .
drwxrwxr-x 13 root me    4096 Nov 14 00:02 ..
-rw-------  1 me me 1163930 Oct 31 23:43 credits.html
-rw-------  1 me me 6266928 Oct 31 23:43 icudtl.dat
drwx------  2 me me    4096 Nov 14 00:02 lib
drwx------  2 me me    4096 Nov 14 00:02 locales
-rw-------  1 me me  437458 Oct 31 23:43 natives_blob.bin
-rwx------  1 me me  195536 Oct 31 23:43 nw
-rw-------  1 me me 1012714 Oct 31 23:43 nw_100_percent.pak
-rw-------  1 me me 5259550 Oct 31 23:43 resources.pak
-rw-------  1 me me  638780 Oct 31 23:43 snapshot_blob.bin
me@hostname /opt/nwjs-v0.13.0-alpha5-linux-x64 $ ./nw
[1114/141335:INFO:nw_package.cc(175)] ./nw
[1:1:1114/141335:FATAL:renderer_main.cc(156)] Failed to load node library (error: libnode.so: cannot open shared object file: No such file or directory)
#0 0x7f7d68f13bde <unknown>


LaunchProcess: failed to execvp:
^C^C
me@hostname /opt/nwjs-v0.13.0-alpha5-linux-x64 $ ll lib
total 96136
drwx------ 2 me me     4096 Nov 14 00:02 .
drwx------ 4 me me     4096 Nov 14 00:06 ..
-rwx------ 1 me me  4282040 Oct 31 23:43 libnode.so
-rwx------ 1 me me 94143352 Oct 31 23:43 libnw.so
me@hostname /opt/nwjs-v0.13.0-alpha5-linux-x64 $ LD_LIBRARY_PATH=$PWD/lib ./nw
[1114/141415:INFO:nw_package.cc(175)] ./nw
[1:1:1114/141416:FATAL:renderer_main.cc(156)] Failed to load node library (error: libnode.so: cannot open shared object file: No such file or directory)
#0 0x7fa7bebc0bde <unknown>


LaunchProcess: failed to execvp:
^C^C
me@hostname /opt/nwjs-v0.13.0-alpha5-linux-x64 $

[Roger Wang]

Please use '--no-sandbox' in command line as workaround. This will be fixed in the next version.

Roger

...