In this section we will learn Electron
the professional terminology often used in development.
ASAR
ASAR
Atom Shell Archive Format
(Atom Shell Archive Format), an ASAR
archive is simply a .tar
file, that is, related text files formatted into a single file . And Electron
can read any files in it without decompressing the entire file.
The format was created ASAR
primarily to improve Windows
performance on the platform .
Brightray
Simply apply libchromiumcontent to your application as a static library, a term specifically developed for use with Electron.
DMG
DMG
Refers to MacOS
the disk image packaging format of the Apple system used on the Internet. DMG
Files are typically used to distribute application installers. electron-builder
Supports using dmg
as a compilation target.
IPC
IPC
Representation Inter-Process Communication
(inter-process communication). Electron
Used to IPC
send serialized JSON
messages between the main process and the renderer process.
CRT
CRT
(i.e. C
runtime library) is part of ISO C99
the standard library that contains C++
the standard library. The library that implements it Visual C++
supports native code development as well as mixed native and managed code. It is also used to .NET
develop purely managed code.
DO
An input method editor is a program that allows the user to enter characters and symbols that are not found on the keyboard . For example, enabling users to type Chinese, Japanese, Korean, and Indian text with a Latin keyboard.
libchromiuncontent
A single open source library that contains Chromium
the module and all dependencies .
main process
The main process, generally refers to main.js
a file, which is Electron
the entry file for each application. It controls the entire App
life cycle, from start to finish. It also manages native elements of the system, such as menus, menu bars, Dock
columns, trays, etc. The main process is mainly responsible for APP
each rendering process created, and the entire Node API
process is integrated into it.
The main process file of each APP
is defined in package.json
the main
properties, so electron .
it can be known which file should be used to start.
native modules
Native modules ( Node.js
also called in addons
) are modules that are used C
or C++
written and can be Node.js
loaded in or loaded Electron
using require()
methods in. It is primarily a library for bridging libraries JavaScript
running on .Node.js
C/C++
Electron
Native Node
modules are supported, but Electron
it is very possible to install a different V8
engine through binary encoding, so you need to specify specific local header files Node
when packaging native modules .Electron
BUT
MAS
Mac
An abbreviation that refers to the App Store on Apple systems .
NSIS
NSIS
It is Nullsoft Scriptable Install System
the abbreviation of (nullsoft script installation system), which is a Windows
script-driven installation and production tool on the Microsoft platform.
process
A process is an instance of a computer program executing. In Node.js
and Electron
, each running process contains an process
object. As a global object, this object provides relevant information and operation methods of the current process. require()
As a global variable, it can be accessed at any time within the application .
renderer process
The rendering process is a browser window in our application. It is different from the main process in that it can exist multiple at the same time and run in different processes. They can also be hidden.
Squirrel
Squirrel
It is an open source framework that enables Electron
applications to be automatically updated to new versions.
userland
userland
Or userspace
the term originated from Unix
the community, when a program runs outside the operating system kernel.
v8
v8
It is Google's open source JavaScript
engine, C++
written and used in Google Chrome. V8
Can run standalone or embedded in any C++
application.
webview
webview
For integrating guest
(guest) content within our Electron
app, something like iframe
. But the difference is that each one webview
runs in a separate process. As a page, it has different permissions and all interactions between embedded content and applications are asynchronous, which ensures the security of our applications for embedded content.
Reprinted from: electron glossary - Zhihu