Houveram algumas atualizações e conversações interessantes sobre o Electron recentemente, aqui está um resumo geral.

Fonte​

O Electron agora está atualizado com o Chrome 45 a partir de v0.32.0. Outras atualizações incluem...

Melhor Documentação​

Reestruturamos e normalizamos a documentação para melhor visualização e melhor leitura. Também há traduções da documentação que contribuem para a comunidade, como japonês e coreano.

Requests pull relacionados: electron/electron#2028, electron/electron#2533, electron/electron#2557, electron/electron#2709, electron#2725, electron#2698, electron/electron#2649.

Node.js 4.1.0​

Desde v0.33.0 o Electron vem com Node.js 4.1.0.

Pul request relacionado: electron/electron#2817.

node-pre-gyp​

Módulos que dependem de node-pre-gyp agora podem ser compilados contra Electron ao construir a partir da fonte.

Related pull request: mapbox/node-pre-gyp#175.

Suporte ARM​

O Electron agora fornece compilações para Linux no ARMv7. Ele é executado em plataformas populares como Chromebook e Raspberry Pi 2.

Problemas relacionados: atom/libchromiumcontent#138, electron/electron#2094, electron/electron#366.

Janela sem Frame estilo de Yosemit​

Um ‘patch’ de @jaanus foi mesclado que, como os outros aplicativos integrados do OS X, permite criar janelas sem frames com os semáforos do sistema integrados no OS X Yosemite e posteriormente.

Pull request relacionado: electron/electron#2776.

Suporte à Impressão do Google Summer of Code​

Após o Google Summer of Code , fizemos merge dos patches por @hokein para melhorar o suporte à impressão. e adicione a possibilidade de imprimir a página em arquivos PDF.

Problemas relacionados: electron/electron#2677, electron/electron#1935, electron/electron#1532, electron/electron#805, electron/electron#1669, electron/electron#1835.

Atom​

Atom agora foi atualizado para Electron v0.30.6 rodando Chrome 44. Uma atualização para v0.33.0 está em progresso no atom/atom#8779.

Talks​

O GitHubber Amy Palamountain fez uma excelente introdução ao Electron em uma palestra em Nordic.js. Ela também criou a biblioteca electron-accelerator.

Construindo aplicações nativas com Electron por Amy Palomountain​

Ogle, também na equipe Atom , falou com Electron na YAPC Asia:

Construindo Aplicativos de Desktop com Tecnologias Web por Ben Ogle​

O membro da Atom da equipe Kevin Sawicki e outros deram palestras sobre o Electron na plataforma Bay são recentemente o Grupo de Usuários Electron. Os vídeos foram postados, aqui estão alguns:

A História do Electron por Kevin Sawicki​

Fazendo com que um aplicativo da web pareça nativo por Ben Gotow​

Join us September 29th at GitHub's HQ for an Electron meetup hosted by Atom team members @jlord and @kevinsawicki. There will be talks, food to snack on, and time to hangout and meet others doing cool things with Electron. We'll also have a bit of time to do lightning talks for those interested. Hope to see you there!

Talks

• Jonathan Ross and Francois Laberge from Jibo will share how they use Electron to animate a robot.
• Jessica Lord will talk about building a teaching tool, Git-it, on Electron.
• Tom Moor will talk about the pros and cons of building video and screen sharing on Electron with speak.io.
• Ben Gotow will preview N1: The Nylas Mail Client and talk about developing it on Electron.

Detalhes​

• Location: GitHub HQ, 275 Brannan Street, San Francisco, CA, 94107
• Date: Tuesday, September 29th, 2015
• Time: 6pm - 9pm
• RSVP: ti.to/github-events/electron-meetup

This week we've given Electron's documentation a home on electronjs.org. You can visit /docs/latest for the latest set of docs. We'll keep versions of older docs, too, so you're able to visit /docs/vX.XX.X for the docs that correlate to the version you're using.

You can visit /docs to see what versions are available or /docs/all to see the latest version of docs all on one page (nice for cmd + f searches).

If you'd like to contribute to the docs content, you can do so in the Electron repository, where the docs are fetched from. We fetch them for each minor release and add them to the Electron site repository, which is made with Jekyll.

If you're interested in learning more about how we pull the docs from one repository to another continue reading below. Otherwise, enjoy the docs!

The Technical Bits​

We're preserving the documentation within the Electron core repository as is. This means that electron/electron will always have the latest version of the docs. When new versions of Electron are released, we duplicate them over on the Electron website repository, electron/electronjs.org.

script/docs​

To fetch the docs we run a script with a command line interface of script/docs vX.XX.X with or without the --latest option (depending on if the version you're importing is the latest version). Our script for fetching docs uses a few interesting Node modules:

• nugget for getting the release tarball and saving it to a temporay directory.
• gunzip-maybe to unzip the tarball.
• tar-fs for streaming just the /docs directory from the tarball and filtering and processing the files (with the help of through2) so that they work nicely with our Jekyll site (more on that below).

Tests help us know that all the bits and pieces landed as expected.

Jekyll​

The Electron website is a Jekyll site and we make use of the Collections feature for the docs with a structure like this:

electron.atom.io
└── _docs
    ├── latest
    ├── v0.27.0
    ├── v0.26.0
    ├── so on
    └── so forth

Material inicial​

For Jekyll to render each page it needs at least empty front matter. We're going to make use of front matter on all of our pages so while we're streaming out the /docs directory we check to see if a file is the README.md file (in which case it receives one front matter configuration) or if it is any other file with a markdown extension (in which case it receives slightly different front matter).

Each page receives this set of front matter variables:

---
version: v0.27.0
category: Tutorial
title: 'Quick Start'
source_url: 'https://github.com/electron/electron/blob/master/docs/tutorial/quick-start.md'
---

The README.md gets an additional permalink so that has a URL has a common root of index.html rather than an awkward /readme/.

permalink: /docs/v0.27.0/index.html

Config and Redirects​

In the site's _config.yml file a variable latest_version is set every time the --latest flag is used when fetching docs. We also add a list of all the versions that have been added to the site as well as the permalink we'd like for the entire docs collection.

latest_version: v0.27.0
available_versions:
  - v0.27.0
collections:
  docs: { output: true, permalink: '/docs/:path/' }

The file latest.md in our site root is empty except for this front matter which allows users to see the index (aka README) of the latest version of docs by visiting this URL, electron.atom.io/docs/latest, rather than using the latest version number specifically (though you can do that, too).

---
permalink: /docs/latest/
redirect_to: /docs/{{ site.data.releases[0].version }}
---

Layouts​

In the docs.html layout template we use conditionals to either show or hide information in the header and breadcrumb.

{% raw %} {% if page.category != 'ignore' %}
<h6 class="docs-breadcrumb">
  {{ page.version }} / {{ page.category }} {% if page.title != 'README' %} / {{
  page.title }} {% endif %}
</h6>
{% endif %} {% endraw %}

To create a page showing the versions that are available we just loop through the list in our config on a file, versions.md, in the site's root. Also we give this page a permalink: /docs/

{% raw %} {% for version in site.available_versions %} - [{{ version
}}](/docs/{{ version }}) {% endfor %} {% endraw %}

Hope you enjoyed these technical bits! If you're interested in more information on using Jekyll for documentation sites, checkout how GitHub's docs team publishes GitHub's docs on Jekyll.

Atom Shell is now called Electron. Você pode aprender mais sobre o Electron e o que as pessoas estão fazendo com ele em sua nova home electronjs.org.

Electron é o shell de aplicação multi-plataforma originalmente construído para o Editor Atom lidar com a integração de loop de eventos Chromium/Node.js e APIs nativas.

When we got started, our goal wasn't just to support the needs of a text editor. We also wanted to create a straightforward framework that would allow people to use web technologies to build cross-platform desktop apps with all of the native trimmings.

In two years, Electron has grown immensely. It now includes automatic app updates, Windows installers, crash reporting, notifications, and other useful native app features — all exposed through JavaScript APIs. And we have more in the works. We plan to extract even more libraries from Atom to make building a native app with web technologies as easy as possible.

So far, individual developers, early-stage startups, and large companies have built apps on Electron. They've created a huge range of apps — including chat apps, database explorers, map designers, collaborative design tools, and mobile prototyping apps.

Check out the new electronjs.org to see more of the apps people have built on Electron or take a look at the docs to learn more about what else you can make.

If you've already gotten started, we'd love to chat with you about the apps you're building on Electron. Email info@electronjs.org to tell us more. You can also follow the new @ElectronJS Twitter account to stay connected with the project.

⚡ 💙 🔌