NW.js will continue supporting Chrome Apps

[Roger Wang]

Today our upstream made an announcement about their plan on Chrome Apps, in which Chrome Apps will not be supported on Win, Linux and macOS.

NW.js can run Chrome Apps directly and we'll continue supporting it. Chrome App developers can redistribute their application after packaging with NW.

Staring from version 0.13, NW.js brings most features in the Chromium browser, including Chrome Apps support, chrome. platform APIs. We support all `chrome.` API in the Chrome App platform. In addition, we support some chrome.* API in the Extension Platform.

Chrome Apps can be run directly on NW. Clone the sample apps repository and run one of them with:

$ /path/to/nw.exe <folder path of the manifest.json file>

or drag the folder to the NW executable. And of course Node.js APIs can be accessed from Chrome App: add “node” permission to manifest.json and you are ready to call nw.require().

For more information, see What's new in 0.13

[steven...@gmail.com]

I really liked how I was able to port my app over from a chrome app to NWJS.

Now my concern is from what I see in the docs and not mentioned in the post that pledged dedication to support chrome apps:

"NW.js is based on Chromium, which also enables you to use Chrome specific features. Such as File System API, experimental CSS styles with -webkit- prefix. Be careful with these non-standard features since they may be deprecated shortly."

I am specifically concerned about losing the FileSystem API as I have a good chunk of code dedicated to syncing files.  Do you know why the Filesystem API has been noted to be potentially deprecated? and would this be a deprecation on the chromium side? 

Steven

[Roger]

The doc is misleading and should be fixed. We don't see any info that File System API will deprecated in Chrome.

btw, Chrome apps can run directly in NW without any change.

Roger

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

[mirza...@gmail.com]

I tried my packaged app to run with:

open -n -a nwjs --args /Users/mirzadelic/Projects/caffetouch

in mac, but gcm doesn't work, can't get reg id from chrome.gcm.register api.

Any suggestion?

[Roger]

The gcm API is a special case: try adding --enable-gcm switch.

--

[mirza...@gmail.com]

And it will be supported even when google disable chrome app support for mac, win and linux?

[Roger]

Right. We'll support them longer than upstream.

[wox...@gmail.com]

typo: Staring should be Starting

also present on the site http://nwjs.io/blog/chrome-apps-support/

On Saturday, August 20, 2016 at 2:47:37 AM UTC+3, Roger Wang wrote:

Staring from version 0.13

[adar...@gmail.com]

Hi All,

I am trying to run existing chrome packaged app in Mac.

my existing chrome packaged app uses PNacl components.

When i tried running chrome app using "nwjs-sdk-v0.18.1-osx-x64" nwjs SDK I am getting below error

"NativeClient: the Portable Native Client (pnacl) component is not installed".

But the my chrome packaged app is working good in Windows using (nwjs-sdk-v0.17.0-win-x64) nwjs SDK.

Could somebody help me in loading Pnacl module in Mac.

Regards,

Adarsh

[akif.m...@rcbenchmark.com]

I want to be able to pack and distribute my chrome app.

How will I be able to achieve that

 

[gillavi...@gmail.com]

Hi! I developed a Chrome app for the first time a few days ago, and when I attempted to publish the app, a message appeared that read "Only supported on ChromeOS". Does this mean I cannot use this app on an ipad platform? 

I was aiming this app towards an ipad platform, and it would break down the purpose of it's creation if it will not work. 

Is there any way I can get it to work on an ipad? this would be extremely helpful, because I am only a beginner when it comes to computer technology. 

Please respond via email hannarobbins2@gmail. I will not know how to access this feed again.

Thank you!