787bc85703
* 📝 Update `README-ko.md` * Remove Korean readme specified header. * Add Indonesia community link. * 📝 Update Korean docs as upstream * 📝 Update Korean docs as upstream * 📝 Update Korean docs as upstream * 📝 Update Korean docs as upstream * 📝 Update Korean docs as upstream * 📝 Mark untranslated docs * 📝 Update Korean docs as upstream [ci skip] * 📝 Update Korean docs as upstream [ci skip] * 📝 Add untranslated files [ci skip] * 📝 Update Korean docs as upstream [ci skip] * 📝 Update Korean docs as upstream * 📝 Update `README-ko.md` * Remove Korean readme specified header. * Add Indonesia community link. * 📝 Update Korean docs as upstream * 📝 Update Korean docs as upstream * 📝 Update Korean docs as upstream * 📝 Update Korean docs as upstream * 📝 Update Korean docs as upstream * 📝 Mark untranslated docs * 📝 Update Korean docs as upstream [ci skip] * 📝 Update Korean docs as upstream [ci skip] * 📝 Add untranslated files [ci skip] * 📝 Update Korean docs as upstream [ci skip] * 📝 Update Korean docs as upstream * 📝 Correct readme name [ci skip] * 📝 Update Korean docs as upstream [ci skip]
64 lines
4.5 KiB
Markdown
64 lines
4.5 KiB
Markdown
> 이 문서는 아직 Electron 기여자가 번역하지 않았습니다.
|
|
>
|
|
> Electron에 기여하고 싶다면 [기여 가이드](https://github.com/electron/electron/blob/master/CONTRIBUTING-ko.md)를
|
|
> 참고하세요.
|
|
>
|
|
> 문서의 번역이 완료되면 이 틀을 삭제해주세요.
|
|
|
|
# About Electron
|
|
|
|
[Electron](http://electron.atom.io) is an open source library developed by GitHub for building cross-platform desktop applications with HTML, CSS, and JavaScript. Electron accomplishes this by combining [Chromium](https://www.chromium.org/Home) and [Node.js](https://nodejs.org) into a single runtime and apps can be packaged for Mac, Windows, and Linux.
|
|
|
|
Electron began in 2013 as the framework on which [Atom](https://atom.io), GitHub's hackable text editor, would be built. The two were open sourced in the Spring of 2014.
|
|
|
|
It has since become a popular tool used by open source developers, startups, and established companies. [See who is building on Electron](/apps).
|
|
|
|
Read on to learn more about the contributors and releases of Electron or get started building with Electron in the [Quick Start Guide](../quick-start).
|
|
|
|
## Core Team and Contributors
|
|
|
|
Electron is maintained by a team at GitHub as well as a group of [active contributors](https://github.com/electron/electron/graphs/contributors) from the community. Some of the contributors are individuals and some work at larger companies who are developing on Electron. We're happy to add frequent contributors to the project as maintainers. Read more about [contributing to Electron](https://github.com/electron/electron/blob/master/CONTRIBUTING.md).
|
|
|
|
## Releases
|
|
|
|
[Electron releases](https://github.com/electron/electron/releases) frequently. We release when there are significant bug fixes, new APIs or are updating versions of Chromium or Node.js.
|
|
|
|
### Updating Dependencies
|
|
|
|
Electron's version of Chromium is usually updated within one or two weeks after a new stable Chromium version is released, depending on the effort involved in the upgrade.
|
|
|
|
When a new version of Node.js is released, Electron usually waits about a month before upgrading in order to bring in a more stable version.
|
|
|
|
In Electron, Node.js and Chromium share a single V8 instance—usually the version that Chromium is using. Most of the time this _just works_ but sometimes it means patching Node.js.
|
|
|
|
|
|
### Versioning
|
|
|
|
Due to the hard dependency on Node.js and Chromium, Electron is in a tricky versioning position and [does not follow `semver`](http://semver.org). You should therefore always reference a specific version of Electron. [Read more about Electron's versioning](http://electron.atom.io/docs/tutorial/electron-versioning/) or see the [versions currently in use](https://electron.atom.io/#electron-versions).
|
|
|
|
### LTS
|
|
|
|
Long term support of older versions of Electron does not currently exist. If your current version of Electron works for you, you can stay on it for as long as you'd like. If you want to make use of new features as they come in you should upgrade to a newer version.
|
|
|
|
A major update came with version `v1.0.0`. If you're not yet using this version, you should [read more about the `v1.0.0` changes](http://electron.atom.io/blog/2016/05/11/electron-1-0).
|
|
|
|
## Core Philosophy
|
|
|
|
In order to keep Electron small (file size) and sustainable (the spread of dependencies and APIs) the project limits the scope of the core project.
|
|
|
|
For instance, Electron uses just the rendering library from Chromium rather than all of Chromium. This makes it easier to upgrade Chromium but also means some browser features found in Google Chrome do not exist in Electron.
|
|
|
|
New features added to Electron should primarily be native APIs. If a feature can be its own Node.js module, it probably should be. See the [Electron tools built by the community](http://electron.atom.io/community).
|
|
|
|
## History
|
|
|
|
Below are milestones in Electron's history.
|
|
|
|
| :calendar: | :tada: |
|
|
| --- | --- |
|
|
| **April 2013**| [Atom Shell is started](https://github.com/electron/electron/commit/6ef8875b1e93787fa9759f602e7880f28e8e6b45).|
|
|
| **May 2014** | [Atom Shell is open sourced](http://blog.atom.io/2014/05/06/atom-is-now-open-source.html). |
|
|
| **April 2015** | [Atom Shell is re-named Electron](https://github.com/electron/electron/pull/1389). |
|
|
| **May 2016** | [Electron releases `v1.0.0`](http://electron.atom.io/blog/2016/05/11/electron-1-0).|
|
|
| **May 2016** | [Electron apps compatible with Mac App Store](http://electron.atom.io/docs/tutorial/mac-app-store-submission-guide).|
|
|
| **August 2016** | [Windows Store support for Electron apps](http://electron.atom.io/docs/tutorial/windows-store-guide).|
|