Renamed browser-side to main process
renamed a few occurances of "web page" to "renderer" renamed a few files that had "browser" in their name to "main-process" note that there are still many occurances of web page.
This commit is contained in:
parent
1804466334
commit
b6875ad49b
15 changed files with 103 additions and 111 deletions
|
@ -5,14 +5,14 @@ atom-shell, and third-party node modules are fully supported too (including the
|
|||
[native modules](../tutorial/using-native-node-modules.md)).
|
||||
|
||||
Atom-shell also provides some extra built-in modules for developing native
|
||||
desktop applications. Some modules are only available on the browser side, some
|
||||
are only available on the client (renderer) side, and some can be used on both sides.
|
||||
desktop applications. Some modules are only available on the main process, some
|
||||
are only available on the renderer process, and some can be used on both processes.
|
||||
The basic rule is: if a module is GUI or low-level system related, then it should
|
||||
be only available on the browser side. You need to be familiar with the concept of
|
||||
[browser-side vs. client-side](../tutorial/quick-start.md#the-browser-side) scripts
|
||||
to be able to use those modules.
|
||||
be only available on the main process. You need to be familiar with the concept of
|
||||
[main process vs. renderer process](../tutorial/quick-start.md#the-main-process)
|
||||
scripts to be able to use those modules.
|
||||
|
||||
The browser-side script is just like a normal `node.js` script:
|
||||
The main process script is just like a normal `node.js` script:
|
||||
|
||||
```javascript
|
||||
var app = require('app');
|
||||
|
@ -24,7 +24,6 @@ app.on('ready', function() {
|
|||
window = new BrowserWindow({width: 800, height: 600});
|
||||
window.loadUrl('https://github.com');
|
||||
});
|
||||
|
||||
```
|
||||
|
||||
The web page is no different than a normal web page, except for the extra
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue