Electron App Architecture. Electron builder (for packaging up your app) Easy redux undo (for undo/redoing your redux actions) Roadmap. There are a number of additions that I'd like to implement in this repository, namely auto-updating and more release-focused enhancements and test suites, but those are lower priority (but I welcome PRs!). Architecture An Electron app always has one main process, but never more. Since Electron uses Chromium for displaying web pages, Chromium's multi-process architecture is also used. Each web page in Electron runs in its own process, which is called the renderer process . electron-packager <location of project> <name of project> <platform> <architecture> <electron version> <optional options> where: location of project points to the folder where your project is,
An Electron app is no less secure than any other application hosted on a person's computer. If a nefarious individual gains access to your computer it really doesn't matter if your application is in Electron, WPF, or any other technology. They can find a way to use the application against the user. Hi, I have a few questions about the electron app structure. On the separation of concerns. Lets take a simple functionality : I would like to list all files (recursively) in a folder and for each of those files perform an http request and display the result of the request for each of those files in a table. Now, if I perform the directory scan in the window process, it will freeze the layout.
The end result should be an electron app under your /bin/desktop folder.. He is a consultant for large and medium-sized companies, organizations and agencies for software architecture, web- and cross-platform development. You can find Gregor often on the road attending or speaking at international conferences.
Learn how to wrap your web app with Electron, access all the APIs, and generate installers. Explore the Electron APIs. The Electron API Demos app interactively demonstrates the most important features of the Electron API. See what's possible with Electron with sample code and helpful tips for building your app. Hi, I have a few questions about the electron app structure. On the separation of concerns. Lets take a simple functionality : I would like to list all files (recursively) in a folder and for each of those files perform an http request and display the result of the request for each of those files in a table. Now, if I perform the directory scan in the window process, it will freeze the layout. electron-packager <location of project> <name of project> <platform> <architecture> <electron version> <optional options> where: location of project points to the folder where your project is, One of the things I wanted to do was build the Electron Application for Windows on my Linux development box, which runs Debian. I used electron-builder for building the app. In this post I'll focus on making electron-builder build the app for windows and will ignore setting up electron, electron-builder and making the electron app. TL;DR
