![]() ![]() Starting from this version, the official documentation is maintained in the same repo we use for development, and is available in. See the official document for this feature for more information. NW will report the file is corrupted and quit immediately. If users or 3rd party modified the files. The public key is built into your NW.js binary. Given a keypair, you sign the application files and redistribute the signature file with your application. The new feature 'content verification', or 'app signing', prevents loading unsigned files with your official binary. ![]() See the doc for more information.Ī sample IDE for debugging mobile web page on the desktop Content Verification Besides opening a new devtools window, You can also place the devtools UI in a webview. To use them, see the guide here.ĭebugging React App easily with React Devtools ExtensionĪ method is added to webview tag, so you can launch devtools for this webview. NW.js is now able to fully support devtools extensions, including the one for ReactJS etc. Full DevTools Extension Support and Embed Devtools as Part of Your App See more information in the announcement. In windows you'll need to replace a file installed by Node. In Linux and OSX you can just load the native module built for Node.js directly. The previous tool to build them for NW.js - 'nw-gyp' is not needed any more. Native modules built for Node.js can be loaded into NW.js now. Below are some samples:Ĭlipper made by Adam Lynch with the Transparency feature in NW Better Native Node.js Module Support With the new browser component based architecuture (see "under the hood" section below), we are now able to provide many features in the Chromium browser, including print preview, PDF viewer and SSL client certificates. NW.js application develpers have been asking for more browser features and compatibility between NW.js and Chromium upstream. For more information, see Security in NW.js. Untrusted contents are still running in the same security model from Chromium browser. You can access all the chrome.* APIs without declaring permission in manifest, load all Node.js libraries and DOM operations are not limited by cross origin checks and CSP any more. The native security model tries to provide you the maximum capability as in a traditional C++ desktop application. Apps that has “node” permission in ‘manifest.json’ is a NW App. They run in different security model: Chrome Apps run in the same model from Chromium upstream NW App runs in the native “Node” security model provided by NW platfrom. The one with a ‘manifest.json’ file is a Chrome App (with an exception below), while NW App is the one with ‘package.json’. ![]() So NW supports 2 kinds of applications now: Chrome Apps and NW Apps. Also see thousands of Chrome Apps online.Īnd 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(). CRX packaging for Chrome Apps is not supported but you can use the packaging mechanisms provided by NW. Clone the sample apps repository and run one of them with: $ /path/to/nw.exe That means many Chrome Apps can be run directly on NW. ![]() Previously in 0.12 we used the new code cache feature in the V8 engine to improve JS source code compilaton Chrome (Packaged) App supportĪfter supporting many chrome.* APIs, the manifest spec for Chrome Apps are also supported in straightforward way. NW developers follows upstream changes closely and bring them to the application developers. There is document tracks the list of them. In addition, we support some chrome.* API in the Extension Platform. See the upstream docs for the listing of chrome APIs: we support all chrome.* API in the Chrome App platform. With rich notifications you can put buttons, lists, images, icon and progress bar in the notification. Including rich notification, context menu, usb, etc. In this version we bring even more of chrome.* API. In previous 0.12 version we started to support chrome.webRequest API to let you intercept network requests made by DOM. Full DevTools Extension Support and Embed Devtools as Part of Your App.This post introduces the following topics for the new release: We also expect faster release cycle and better stability with the new architecture in 2016. This is done by following upstream closely with an adjusted architecture. NW.js v0.13 brings most features in the Chromium browser, including Chrome Apps support, chrome.* platform APIs, NaCl and Pepper plugin, builtin PDF viewer, printing preview, rich notifications and many more. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |