update excerpts based on feedback
This commit is contained in:
parent
0527b17e42
commit
2c8261b429
8 changed files with 12 additions and 12 deletions
|
@ -1,6 +1,7 @@
|
|||
# contentTracing
|
||||
|
||||
> Debug your application using Chromium's content module.
|
||||
> Collect tracing data from Chromium's content module for finding performance
|
||||
bottlenecks and slow operations.
|
||||
|
||||
This module does not include a web interface
|
||||
so you need to open `chrome://tracing/` in a Chrome browser and load the
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
# desktopCapturer
|
||||
|
||||
> Capture audio, video, and images from a microphone, camera, or
|
||||
screen using the `getUserMedia` API.
|
||||
> List `getUserMedia` sources for capturing audio, video, and images from a
|
||||
microphone, camera, or screen.
|
||||
|
||||
```javascript
|
||||
// In the renderer process.
|
||||
|
|
|
@ -1,9 +1,9 @@
|
|||
# DownloadItem
|
||||
|
||||
> Trigger file downloads from remote sources.
|
||||
> Control file downloads from remote sources.
|
||||
|
||||
`DownloadItem` is an EventEmitter represents a download item in Electron. It
|
||||
is used in `will-download` event of `Session` module, and allows users to
|
||||
`DownloadItem` is an EventEmitter that represents a download item in Electron.
|
||||
It is used in `will-download` event of `Session` module, and allows users to
|
||||
control the download item.
|
||||
|
||||
```javascript
|
||||
|
|
|
@ -1,7 +1,6 @@
|
|||
# protocol
|
||||
|
||||
> Register a custom protocol to intercept click events from other running
|
||||
applications.
|
||||
> Register a custom protocol and intercept existing protocols.
|
||||
|
||||
An example of implementing a protocol that has the same effect as the
|
||||
`file://` protocol:
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
# remote
|
||||
|
||||
> Communicate between the renderer process and the main process.
|
||||
> Use main process modules from the renderer process.
|
||||
|
||||
The `remote` module provides a simple way to do inter-process communication
|
||||
(IPC) between the renderer process (web page) and the main process.
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
# session
|
||||
|
||||
> Manage browser cookies, cache, and other session data.
|
||||
> Manage browser sessions, cookies, cache, proxy settings, etc.
|
||||
|
||||
The `session` module can be used to create new `Session` objects.
|
||||
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
# Synopsis
|
||||
|
||||
> Info about Node.js and the main and renderer processes.
|
||||
> How to use Node.js and Electron APIs.
|
||||
|
||||
All of [Node.js's built-in modules](http://nodejs.org/api/) are available in
|
||||
Electron and third-party node modules also fully supported as well (including
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
# webContents
|
||||
|
||||
> Render and control web pages using lifecycle events.
|
||||
> Render and control web pages.
|
||||
|
||||
`webContents` is an
|
||||
[EventEmitter](http://nodejs.org/api/events.html#events_class_events_eventemitter).
|
||||
|
|
Loading…
Reference in a new issue