![]() ![]() This means that communication between windows or between the main process and the renderer processes is a bit harder. A main process is started and that main process can open windows with separate renderer processes. While this requires more work from the NW.js developers, it means the browser and Node environments interact in a more seamless way.Įlectron does things in a very different way. In more technical terms, this means that the NW.js team has to insert some hooks in the Chromium codebase so it can plug in the Node.js environment. It starts a Node.js runtime which then has the ability to open windows into which you can then load web pages. This means that it can be directly accessed from the DOM of all open windows transparently.Įlectron, on the other end, has more of a Node.js-oriented approach. If more than one window is opened, then they all get access to that shared Node.js context. It basically loads the specified HTML page and that page gets access to the Node.js context. It is a bit of an over-simplification but, broadly speaking, NW.js’ paradigm is more browser-oriented. There is still some confusion here (see text below). If you would like the Chromium team to improve kiosk mode support on Mac, please vote for it.Ħ. ![]() Kiosk mode is enabled upstream by Chromium. This can be done by using the “ node-main” instruction in the package.json file or (in version 0.13 and above) through the Chrome Apps manifest file.ĥ. Tests performed on Apple MacBook Pro Retina (Yosemite)Ĥ. The Electron team decided against support for V8 snapshots. It’s basically a TAR archive of all the project files. If you are using a version smaller than 0.22, beware that this results in a 30% performance hit.Ģ. Vorbis, Theora, Opus, VP8, VP9, PCM, Ogg, WebM, WAVġ. The Chartģ2bit (Win), 64bit (Win/Mac) & arm (limited) In addition to the chart, I will also compile a list of various other key differences that may influence a first-time user’s choice. Please (respectfully) leave your comments, suggestions and corrections to make this comparison as accurate as possible. I must confess that I have used NW.js quite a bit more than Electron, so this post may suffer from my own bias. Hopefully, the chart and comments in this article will help you choose the right tool to build your next project. However, the release of version 0.13 of NW.js brought on so many improvements that an update became necessary. In 2015, I released a first version of this comparison between the two tools. Deciding which one to go with is not so obvious. ![]() If you wish to create a desktop application from web technologies, the open source world offers two main choices: NW.js (formerly node-webkit) and Electron (formerly atom-shell). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |