![]() Let’s start creating our application that we’ll later compile to a native application. Note: If you really prefer the advantages of Electron, check out SitePoint’s recent article on creating desktop apps with Electron. While Electron opens the door for desktop applications written with JavaScript and without a GUI, NW.js applications are probably easier to set up, in case you just want to display an HTML-based application. Also, closing the GUI won’t close the main process you’ll need to terminate it manually by calling an API method. This means that you could theoretically run Electron apps without a GUI. This JavaScript file is opened in a separate main process, and can then open an HTML file in the GUI. This HTML file will be opened in the GUI directly.Įlectron applications, on the other hand, specify a JavaScript file as their entry point. NW.js applications specify their entry point in the form of an HTML file. NW.js only writes a local file that can then be submitted manually. Automatic crash reporting to a remote server.Built-in auto-updater (you can follow this issue about an auto-updater for NW.js).However, Electron also has some advantages worth mentioning: They are used to write multi-threaded applications. Supports Node.js integration in Web Workers.Using the nwjc tool, your code will be compiled to native code. Has a V8 snapshot source code protection, used to secure your application’s source code.(See this tutorial about how to use them in NW.js.) They focus on performance and are therefore primarily written in C and C++. Supports NaCl (Native Client) and PNaCl (Portable Native Client) applications.But according to this post NW.js will still support Chrome apps.) (Chromium will remove its support until August, 2018 (see their blog post). (More info in the Chrome developer docs.) These applications are different from NW.js, because they have no Node.js integration and are published using the Chrome Web Store. Chrome apps are packaged applications that are written with web languages. (You can find more information about this in the NW.js docs.) These APIs can be used to interact with the browser. Here are the advantages of NW.js compared to Electron: Now you might be interested in the differences between them. It started in 2013, two years after NW.js, but because it’s from GitHub it quickly became well known. There’s another competitor called Electron. An example application that was built using the instructions from this article can be found on GitHub.Īdvantages of NW.js in Comparison to Electronįirst, there’s one thing to mention: NW.js isn’t the only framework for hybrid apps. In this article, we’ll become familiar with NW.js in practice and learn how to create a hybrid application. the option to customize the entire window (close buttons, menu bar) and context menus. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |