No description
d63de1ae15
In browser process, because of the use of v8::Locker in ProxyResolverV8, creating HandleScope requires entering locker first, so in browser process we should just use v8::Locker whenever we need to use V8 in a callback called from non-V8 places (like dialog's callback, work pushed to MessageLoop). But also notice that the renderer process doesn't use v8::Locker, so we have to be careful not to use it, otherwise blink would crash when creating HandleScope. |
||
---|---|---|
app | ||
browser | ||
common | ||
docs | ||
renderer | ||
script | ||
spec | ||
tools | ||
vendor | ||
.gitignore | ||
.gitmodules | ||
atom.gyp | ||
common.gypi | ||
filename_rules.gypi | ||
LICENSE | ||
package.json | ||
README.md |
Atom Shell
Native layer for the Atom editor.
Features
- Write desktop applications with web techniques
- Support built-in and third-party modules of node.js
- Support native node.js modules
- Extended built-in modules for desktop programming
- JavaScript on browser side
- Easy API for cross-process communication
Usage & Development
See the docs here.
License
See the LICENSE
file.