mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

Capitilization, grammar, and punctuation changes

Browse source
This commit is contained in:
andy matthews 2014-05-07 00:06:35 -05:00
parent a69c312389
commit f263a8e9d5
6 changed files with 51 additions and 51 deletions
Download patch file Download diff file Expand all files Collapse all files

22
docs/development/atom-shell-vs-node-webkit.md
View file

@ -1,15 +1,15 @@
# Technical differences to node-webkit
# Technical differences to Node-Webkit
Like node-webkit, atom-shell provides a platform to write desktop applications
with JavaScript and HTML, and has node integration to grant access to low level
Like Node-Webkit, 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 Node-Webkit:
**1. Entry of application**
In node-webkit, the main entry of an application is a web page, you specify a
In Node-Webkit, 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.
@ -18,7 +18,7 @@ providing a URL directly, you need to manually create a browser window and load
html file in it with corresponding API. You also need to listen to window events
to decide when to quit the application.
So atom-shell works more like the node.js runtime, and APIs are more low level,
So atom-shell works more like the Node.js runtime, and APIs are more low level,
you can also use atom-shell for web testing purpose like
[phantomjs](http://phantomjs.org/),
@ -32,17 +32,17 @@ 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 Node-Webkit, 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
concept of node context and web context, these concepts were invented because
of how the node-webkit was implemented.
If you are an experienced Node-Webkit 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.
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
feature of Node, atom-shell doesn't introduce a new JavaScript context in web
pages.

2
docs/development/build-instructions-linux.md
View file

@ -2,7 +2,7 @@
## Prerequisites
* [node.js](http://nodejs.org)
* [Node.js](http://nodejs.org)
* clang and headers of GTK+ and libnotify
On Ubuntu you could install the libraries via: