NW.js v0.13.0-alpha3 released

[Roger]

(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-alpha3. In this version
Chromium is updated to version 44 and io.js is updated to v3.0.0.

NaCl support is added in this version. Because we migrated to a new
architecture to leverage "browser components" from upstream, it's been
easier to add more features in Chromium. Due to user request, a new
build flavor 'nacl' is added. Now we have 3 builds for each platform
(regular, sdk and nacl).

Major part of Menu API is ported from v0.12 as nw.Menu. Note that the
API is different from v0.12 and we'll create a wrapper for backward
compatibility in beta phase.

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/alpha3/nwjs-v0.13.0-alpha3-win-x64.zip
http://dl.nwjs.io/v0.13.0/alpha3/nwjs-v0.13.0-alpha3-osx-x64.zip
http://dl.nwjs.io/v0.13.0/alpha3/nwjs-v0.13.0-alpha3-linux-x64.tar.gz

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

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

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

[Khebs]

Hi Roger,

I tried to run my existing app which runs fine on 0.12.3 to 0.13.alpha3 (0.13.a*) i get this in my console:

[x] [0825/221535:INFO:nw_package.cc(174)] ./bin/osx/0.13.a3/nwjs.app/Contents/MacOS/nwjs .


[x] [40983:1811:0825/221536:ERROR:bluetooth_adapter_mac.mm(100)] Not implemented reached in virtual bool device::BluetoothAdapterMac::IsDiscoverable() const


child process exited with code 0

and the app stays in process but nothing of my code is executed.

Thanks

[Khebs]

 I also wish to note that I am on OS X Yosemite 10.10.5, also the nwjs wish to communicate to an ip with port 53

On Tuesday, August 25, 2015 at 8:51:40 PM UTC+8, Roger Wang wrote:

[toha....@gmail.com]

Glad to see the version is raise again :D

Is it possible for this 0.13 version to support chrome.serial API too?

I think it will very useful for creating hardware programming tools such as Arduino etc..

[Khebs]

+1 yay

[alex.g...@nextday.fi]

+1 for that, especially since node-serialport does not work with io.js 3.0! (https://github.com/voodootikigod/node-serialport/issues/562)

[alex.g...@nextday.fi]

It'd be great to get to Chromium 45 or up before the final release since 45 added a lot of new ES6/ES2015 functionality.

[Brandon Papworth]

+1 to this. Arrow functions are ALMOST there :)

[plo...@gmail.com]

Are remote host already supported?
I tried specifying in the package.json

{

  "name": "TestNWJS13",

  "description":"Test NWJS v13 alpha"

  ,"main": "http://localhost/my_app"

  //.....

}

but in the shell nw is not defined so i think it's not working or i'm doing something wrong?

[VoidVolker]

What is NaCl?

[Ervin Kosch]

Native Client is a sandbox for running compiled C and C++ code in the browser efficiently and securely, independent of the user’s operating system. Portable Native Client extends that technology with architecture independence, letting developers compile their code once to run in any website and on any architecture with ahead-of-time (AOT) translation.

Source: https://developer.chrome.com/native-client

In plain English you write applications using C, C++ and run them inside a browser.  This similar to what Java is.  The C compiler that Native Client lets you use a LOT of old and powerful libraries.  In essence it lets you do a lot more with the browser then you can do with JavaScript.  

Here is a dicussion on what Native Client is

http://chadaustin.me/2011/01/native-client-is-widely-misunderstood-and-what-google-should-do-about-it/

On Wednesday, September 2, 2015 at 6:55:30 AM UTC-4, VoidVolker wrote:

What is NaCl?

[albert....@gmail.com]

I noticed that there is no scroll bar, is there any way to activate? thanks

[serg...@gmail.com]

Hi Roger. I notice that since 13.0 alpha 0 there has been no binary built for OSX 32 bits (osx-ia32). Is this officially not supported now? If so, is it still possible to build the binary myself, or are there breaking changes?

On Tuesday, August 25, 2015 at 5:51:40 AM UTC-7, Roger Wang wrote:

[moo...@gmail.com]

如何播放video？

在 2015年8月25日星期二 UTC+8下午8:51:40，Roger Wang写道：

[李江]

NW.js v0.13.0-alpha3 released 的版本 好像没有了ffmpegsumo.dll  ！我该如何在项目中播放mp3 或者是mp4 文件呢？

在 2015年8月25日星期二 UTC+8下午8:51:40，Roger Wang写道：

(NOTE: This version is a snapshot of the next major version 0.13 which

[m...@nationstates.net]

Trying to convert a working 0.12.3 nwjs app to 0.13.0-alpha3, I've encountered the following problems on Ubuntu 15.04:

(1) 'var gui = require("nw.gui")' now generates an error: "require is not defined". Fixed by replacing calls like 'gui.Window.get().showDevTools()' with 'nw.Window.get().showDevTools()'.

(2) '"window": { "kiosk": true }' in package.json is ignored. I discovered I can invoke kiosk mode once the app is running with 'nw.Window.get().enterFullScreen()', but I can't make it start in this mode. '"window": { "fullscreen": true }' in package.json is ignored.

(3) '"node-main": <file>' in package.json is ignored. The only way to run code is to invoke it via <script> tags in the HTML file specified by '"main": <file>'. The example on the wiki at https://github.com/nwjs/nw.js/wiki/node-main generates the error: "Uncaught TypeError: process.mainModule.exports.callback0 is not a function".

(4) I can't require my own modules! (Which contain most of my app's code.) In default mode, I get an error: "require is not defined". In --mixed-context mode, I get "Cannot find module: <name>". I've tried every combination of path, prefix, and suffix I can think of, as well as 'nw.require' vs 'require', but nothing can compell nwjs 0.13.0-alpha3 to find a module written by me. I can require third-party modules, e.g. 'var fs = require("fs"). But I can't do 'var MyModule = require("./MyModule")' any more.

Max.

[VoidVolker]

Now all node context in var nw, you need now use nw.require

[m...@nationstates.net]

On Tuesday, September 15, 2015 at 2:23:09 PM UTC+10, VoidVolker wrote:

Now all node context in var nw, you need now use nw.require

Thanks, but like I said, this produces "Cannot find module '<name>'".

> var MyModule = nw.require('./MyModule')
module.js:341 Uncaught Error: Cannot find module './MyModule'
    at Function.Module._resolveFilename (module.js:341:15)
    at Function.Module._load (module.js:286:25)
    at Module.require (module.js:370:17)
    at require (module.js:389:17)
    at <anonymous>:2:19
    at Object.InjectedScript._evaluateOn (<anonymous>:905:140)
    at Object.InjectedScript._evaluateAndWrap (<anonymous>:838:34)
    at Object.InjectedScript.evaluate (<anonymous>:694:21)

[VoidVolker]

And what real path to your module? Did you try

var MyModule = nw.require('MyModule')

Or try sysinternals procmon to check where module is searching.

[Brandon Papworth]

You said you had tried all path combinations and the like, but have you tried something like this:

var path = nw.require('path');
var someModule = nw.require(path.join(nw.__dirname, './dirs/to/some_module'));

That will get you an absolute path to the module relative to the nwjs root (where your package.json is).

[m...@nationstates.net]

Thanks, yes, I have tried. In the debugger:

> var Game = nw.require(path.join(nw.__dirname, './js/Game'))
module.js:341 Uncaught Error: Cannot find module '/home/max/code/<appname>/js/Game'

Yet from the command line:

$ ls -l /home/max/code/<appname>/js/Game.js
-rw-rw-r-- 1 max max 2888 Sep 15 12:22 /home/max/code/<appname>/js/Game.js

Same deal with every alternative I can think of, e.g.
> var Game = nw.require('./js/Game')   // This works with regular 'require' in nwjs 0.12.3
> var Game = nw.require('./js/Game.js')
> var Game = nw.require('Game')
> var Game = nw.require('Game.js')
> var Game = nw.require('./Game')
> var Game = nw.require('./Game.js')
> var Game = nw.require('/home/max/code/<appname>/js/Game')
> var Game = nw.require('/home/max/code/<appname>/js/Game.js')
... and more...

All return "Cannot find module."

[hkaya]

Hey Max,

I reported this issue a while back. It's currently assigned to Roger. See https://github.com/nwjs/nw.js/issues/3763.

[m...@nationstates.net]

On Wednesday, September 16, 2015 at 12:47:52 PM UTC+10, hkaya wrote:

I reported this issue a while back. It's currently assigned to Roger. See https://github.com/nwjs/nw.js/issues/3763.

Aha, thank you!

[eric.a...@gmail.com]

+1 for that, I'm at

$ node -v

v4.1.1