No description
7f3620bee3
* Initial commit.
* Do not rely on latest base/template_util.
* Enable modifying existing ObjectTemplate.
* Fix compilation error of function_template.
* Add initial Constructor type.
* Fix passing the wrong parameter.
* Make the Constructor accept arbitrary callback.
* Cleanup.
* Constructor should wrap the this pointer.
* Simplify Wrappable API.
* Remove helper typedefs.
* Support function with 7 parameters.
* Enable converting void*.
* Enable setting method in Dictionary.
* Add v8::Handle<v8::String> to converter.
* Make ScopedPersistent do type conversion.
* Add Arguments.Length method.
* Do not wrap an object when it's already wrapped.
* No need to reset wrapper_ when we would run destructor.
* Call object._init if we have one.
* Add object() accessor for Dictionary.
* Add converter for const char*.
* Enable creating empty Dictionary directly.
* Mark Dictionary.Get as const.
* Strictly check for boolean type.
* Add .gitignore.
* Add APIs to match new V8 APIs.
* Bring back ScopedPersistent.SetWeak.
* Some more APIs fixes.
* Reset handle in weak callback.
This doesn't seem to be neccesary, but we had better follow what upstream does.
* Enable converting ScopedPersistent.
* Fix compilation error with node 0.10.
* Fix compilation error of Constructor and ScopedPersistent in node 0.10.
* Use pump to generate source files.
* Add callback converter.
* Make ScopedPersistent's interface consistent with V8.
* Remove unused constructor of Dictionary.
* Add PersistentDictionary.
* Make throwing exception when parsing args easier
* Use NODE_VERSION_AT_LEAST to determine node version
* Don't throw error in Constructor
* Guard against non-constructor call in Constructor::New
* Fix throwing error in constructor
* Fix ignored exception thrown from constructor.
* OVERRIDE => override
* Avoid unnecessary copy in ConvertToV8
* Check internal field before converting
* Remove unneeded helper
* Add AfterInit method for Wrappable
* Add converter for unsigned long
* usigned long is uint64 on Linux
* Don't reset handle before Wrappable is destroyed
It is possible that the user wants to use the V8 object in the destructor.
Fixes atom/atom-shell#1112.
* added std::set converter
* Use Local instead of Handle
* Pass Handle to upper HandleScope when returning a V8 Handle
* Enter context before calling callback
* Allow converting Array
* Remember isolate in Wrappable
* Make isolate() public
* Check for null when converting Wrappable
* Add IsDestroyed method for Wrappable
* Allow specify methods that can be called after object is destroyed
* Use C++11 version of CreateFunctionTemplate
* Remove callback.h
* Remove locker.h
* Add Dictionary::CreateEmpty
* GetNext should have no side effect when failed
* Don't convert Function to Dictionary
* Don't pass callback as const reference
* Add SetHidden for Dictionary
* Use the new SetWeak in Wrappable
* Check whether key exists in Dictionary::Get
* Don't return v8::Maybe for std::vector
* Add Dictionary::Delete
* Do not manually destroy native resources
* isDestroy => isDestroyed
* Fix converter for std::set
* Improve error message for type error
Close atom/electron#4307.
* Clear internal field when Wrapper is destroyed
* basic_types.h => macros.h
* use v8::private symbols as identifiers for object properties
* Make Wrappable a template class
* Leak Wrappable's template
Since it is declared as static variable it will be released
automatically when process exits, which causes crashes in
renderer process because the template will then be released
later than V8 is closed.
This commit simply leaks the template so the crash won't happen,
this leak should be fine since leaking resource on exit is not
a bad thing.
* Handle.ToV8 should return Object
* Add converter for std::map
* Setup v8::MicrotasksScope for callbacks
* Update to API changes of V8 5.2
* CHECK is not needed
* Call the user call Init in Constructor
* Make InitWith virtual
* Turn Wrappable into using FunctionTemplate
* Create objects from InstanceTemplate
* NewOperatorFactory is not used
* Remove the Constructor class
* GetConstructor should init default constructor
* Pass FunctionTemplate in BuildPrototype
* Do not set constructor name in SetConstructor
* Use ToDetailString for processing error message
* Add back empty handle string
* Add README
* create empty handle for null or undefined value
* Support setting read-only property value
* Add Converter<std::map<std::string, T>>::ToV8
* Add CI build through Electron
* Support 5 argument member function
* Use std functions instead of template_util
* Make Wrappable thread safe
* Use gin to manage FunctionTemplate
Sadly there is no way for us to know when V8 is closing, thus it is
impossible for us to clean the FunctionTemplate on exit at the right
time, which is critcal for multi-thread environment.
* add ability to set high memory usage, skipping the second round of GC callbacks
* Fix broken link
* Add a converter for `nullptr_t`
* Upstream Muon changes to avoid crashing
* only mark handle as independent when it's a high memory user
* Remove WrappableBase::GetWrapper() DCHECK
* virtual members need a virtual destructor
* GetWrapper should be const
* Add support for FreeBSD
* Remove usage of MarkIndependent api
https://bugs.chromium.org/p/chromium/issues/detail?id=780749
Use Active/Not Active as indicator whether the Scavenger can drop wrappers
* Address breaking API
* Fix Value::ToDetailString() call
See https://chromium-review.googlesource.com/848782
* Revert "Address breaking API"
This reverts commit
|
||
|---|---|---|
| .circleci | ||
| .github | ||
| atom | ||
| brightray | ||
| build | ||
| chromium_src | ||
| default_app | ||
| docs | ||
| docs-translations | ||
| lib | ||
| native_mate | ||
| npm | ||
| script | ||
| spec | ||
| tools | ||
| vendor | ||
| .clang-format | ||
| .dockerignore | ||
| .gitignore | ||
| .gitmodules | ||
| .remarkrc | ||
| .travis.yml | ||
| appveyor.yml | ||
| BUILD.gn | ||
| CODE_OF_CONDUCT.md | ||
| common.gypi | ||
| CONTRIBUTING.md | ||
| DEPS | ||
| Dockerfile | ||
| Dockerfile.arm64 | ||
| Dockerfile.arm64v8 | ||
| Dockerfile.armv7 | ||
| Dockerfile.circleci | ||
| electron.gyp | ||
| features.gypi | ||
| filenames.gypi | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| SECURITY.md | ||
| toolchain.gypi | ||
| vsts.yml | ||
📝 Available Translations: 🇨🇳 🇹🇼 🇧🇷 🇪🇸 🇰🇷 🇯🇵 🇷🇺 🇫🇷 🇹🇭 🇳🇱 🇹🇷 🇮🇩 🇺🇦 🇨🇿 🇮🇹. View these docs in other languages at electron/i18n.
The Electron framework lets you write cross-platform desktop applications using JavaScript, HTML and CSS. It is based on Node.js and Chromium and is used by the Atom editor and many other apps.
Follow @ElectronJS on Twitter for important announcements.
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to coc@electronjs.org.
Installation
To install prebuilt Electron binaries, use npm.
The preferred method is to install Electron as a development dependency in your
app:
npm install electron --save-dev [--save-exact]
The --save-exact flag is recommended for Electron prior to version 2, as it does not follow semantic
versioning. As of version 2.0.0, Electron follows semver, so you don't need --save-exact flag. For info on how to manage Electron versions in your apps, see
Electron versioning.
For more installation options and troubleshooting tips, see installation.
Quick start
Clone and run the electron/electron-quick-start repository to see a minimal Electron app in action:
git clone https://github.com/electron/electron-quick-start
cd electron-quick-start
npm install
npm start
Resources for learning Electron
- electronjs.org/docs - all of Electron's documentation
- electron/electron-quick-start - a very basic starter Electron app
- electronjs.org/community#boilerplates - sample starter apps created by the community
- electron/simple-samples - small applications with ideas for taking them further
- electron/electron-api-demos - an Electron app that teaches you how to use Electron
- hokein/electron-sample-apps - small demo apps for the various Electron APIs
Programmatic usage
Most people use Electron from the command line, but if you require electron inside
your Node app (not your Electron app) it will return the file path to the
binary. Use this to spawn Electron from Node scripts:
const electron = require('electron')
const proc = require('child_process')
// will print something similar to /Users/maf/.../Electron
console.log(electron)
// spawn Electron
const child = proc.spawn(electron)
Mirrors
Documentation Translations
Find documentation translations in electron/i18n.
Community
Info on reporting bugs, getting help, finding third-party tools and sample apps, and more can be found in the support document.
License
When using the Electron or other GitHub logos, be sure to follow the GitHub logo guidelines.