From cda129b073351fa6f6f617b1b0409d653ac07b5e Mon Sep 17 00:00:00 2001 From: Suyash Date: Thu, 12 Mar 2015 01:54:59 +0530 Subject: [PATCH] :memo: rename node-webkit to NW.js in development docs Replaces all occurences of node-webkit with NW.js in the development docs. --- docs/README.md | 2 +- ...ell-vs-node-webkit.md => atom-shell-vs-nwjs.md} | 14 +++++++------- 2 files changed, 8 insertions(+), 8 deletions(-) rename docs/development/{atom-shell-vs-node-webkit.md => atom-shell-vs-nwjs.md} (78%) diff --git a/docs/README.md b/docs/README.md index 9f859de9cb8c..bc8a3b6b7e30 100644 --- a/docs/README.md +++ b/docs/README.md @@ -55,7 +55,7 @@ Modules for both sides: * [Coding style](development/coding-style.md) * [Source code directory structure](development/source-code-directory-structure.md) -* [Technical differences to node-webkit](development/atom-shell-vs-node-webkit.md) +* [Technical differences to NW.js](development/atom-shell-vs-nwjs.md) * [Build instructions (Mac)](development/build-instructions-mac.md) * [Build instructions (Windows)](development/build-instructions-windows.md) * [Build instructions (Linux)](development/build-instructions-linux.md) diff --git a/docs/development/atom-shell-vs-node-webkit.md b/docs/development/atom-shell-vs-nwjs.md similarity index 78% rename from docs/development/atom-shell-vs-node-webkit.md rename to docs/development/atom-shell-vs-nwjs.md index 26f04194d970..af4c6ca4da26 100644 --- a/docs/development/atom-shell-vs-node-webkit.md +++ b/docs/development/atom-shell-vs-nwjs.md @@ -1,15 +1,15 @@ -# Technical differences to Node-Webkit +# Technical differences to NW.js -Like Node-Webkit, atom-shell provides a platform to write desktop applications +Like NW.js, atom-shell provides a platform to write desktop applications with JavaScript and HTML, and has Node integration to grant access to low level system in web pages. But there are also fundamental differences between the two projects that make -atom-shell a completely separate product from Node-Webkit: +atom-shell a completely separate product from NW.js: **1. Entry of application** -In Node-Webkit, the main entry of an application is a web page, you specify a +In NW.js, the main entry of an application is a web page, you specify a main page in the `package.json` and it would be opened in a browser window as the application's main window. @@ -32,16 +32,16 @@ need a powerful machine to build atom-shell. **3. Node integration** -In Node-Webkit, the Node integration in web pages requires patching Chromium to +In NW.js, the Node integration in web pages requires patching Chromium to work, while in atom-shell we chose a different way to integrate libuv loop to each platform's message loop to avoid hacking Chromium, see the [`node_bindings`](../../atom/common/) code for how that was done. **4. Multi-context** -If you are an experienced Node-Webkit user, you should be familiar with the +If you are an experienced NW.js user, you should be familiar with the concept of Node context and web context, these concepts were invented because -of how the Node-Webkit was implemented. +of how the NW.js was implemented. By using the [multi-context](http://strongloop.com/strongblog/whats-new-node-js-v0-12-multiple-context-execution/) feature of Node, atom-shell doesn't introduce a new JavaScript context in web