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

Improve grammar and comments

Browse source 
Improve the grammar and sentence structure of the text and improve the code comments.
This commit is contained in:
Jeffrey Morgan 2015-07-14 21:28:57 +01:00 • committed by Cheng Zhao
parent c2bfc60a59
commit 4baaf03ac7
1 changed files with 15 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

27
docs/tutorial/quick-start.md
View file

@ -4,39 +4,40 @@
Electron enables you to create desktop applications with pure JavaScript by providing a runtime with rich native APIs. You could see it as a variant of the io.js runtime which is focused on desktop applications instead of web servers.
It doesn't mean Electron is a JavaScript binding to GUI libraries. Instead,
This doesn't mean Electron is a JavaScript binding to GUI libraries. Instead,
Electron uses web pages as its GUI, so you could also see it as a minimal
Chromium browser, controlled by JavaScript.
### Main process
In Electron, the process that runs `package.json`'s `main` script is called
__the main process__. The script that runs in the main process, can display GUI by
__the main process__. The script that runs in the main process can display a GUI by
creating web pages.
### Renderer process
Since Electron uses Chromium for displaying web pages, Chromium's
multi-processes architecture is also used. Each web page in Electron runs in
multi-process architecture is also used. Each web page in Electron runs in
its own process, which is called __the renderer process__.
In normal browsers web pages usually run in a sandboxed environment and are not
allowed access to native resources. Electron users however, have the power to use
In normal browsers, web pages usually run in a sandboxed environment and are not
allowed access to native resources. Electron users, however, have the power to use
io.js APIs in web pages allowing lower level operating system interactions.
### Differences between main process and renderer process
The main process creates web pages by creating `BrowserWindow` instances. Each `BrowserWindow` instance runs the web page in its own renderer process. When a `BrowserWindow` instance is destroyed, the corresponding renderer process
would also be terminated.
is also terminated.
The main process manages all web pages and their corresponding renderer
processes, each renderer process is isolated and only cares
processes. Each renderer process is isolated and only cares
about the web page running in it.
In web pages, it is not allowed to call native GUI related APIs because managing
native GUI resources in web pages is very dangerous and easy to leak resources.
If you want to do GUI operations in web pages, you have to communicate with
the main process to do it there.
native GUI resources in web pages is very dangerous and it is easy to leak resources.
If you want to perform GUI operations in a web page, the renderer process of the web
page must communicate with the main process to request the main process perform those
operations.
In Electron, we have provided the [ipc](../api/ipc-renderer.md) module for
communication between main process and renderer process. And there is also a
@ -77,7 +78,7 @@ var BrowserWindow = require('browser-window'); // Module to create native brows
require('crash-reporter').start();
// Keep a global reference of the window object, if you don't, the window will
// be closed automatically when the javascript object is GCed.
// be closed automatically when the JavaScript object is GCed.
var mainWindow = null;
// Quit when all windows are closed.
@ -89,8 +90,8 @@ app.on('window-all-closed', function() {
}
});
// This method will be called when Electron has done everything
// initialization and ready for creating browser windows.
// This method will be called when Electron has finished
// initialization and is ready to create browser windows.
app.on('ready', function() {
// Create the browser window.
mainWindow = new BrowserWindow({width: 800, height: 600});