CraftSpace/Notes/Electron.txt at main · publiccodenet/CraftSpace · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
https://openfin.co/2015/12/07/why-were-moving-to-electron/
https://discuss.atom.io/t/electron-vs-brightray-vs-libchromiumcontent-what-to-use-for-following-scenarios/16917
http://www.tivix.com/blog/nwjs-and-electronjs-web-technology-desktop/
https://www.akawebdesign.com/2015/05/06/electron-vs-nwjs/

----

http://electron.atom.io/docs/tutorial/offscreen-rendering/

----

http://electron.atom.io/docs/tutorial/using-native-node-modules/

Manually building for Electron

If you are a developer developing a native module and want to test it
against Electron, you might want to rebuild the module for Electron
manually. You can use node-gyp directly to build for Electron:

cd /path-to-module/
HOME=~/.electron-gyp node-gyp rebuild --target=1.2.3 --arch=x64 --dist-url=https://atom.io/download/electron

The HOME=~/.electron-gyp changes where to find development headers.
The --target=1.2.3 is version of Electron. The --dist-url=...
specifies where to download the headers. The --arch=x64 says the
module is built for 64bit system.

----

Enable Flash Plugin in a <webview> Tag

Add plugins attribute to <webview> tag.

<webview src="http://www.adobe.com/software/flash/about/" plugins></webview>

----