Book Image

Cross-platform Desktop Application Development: Electron, Node, NW.js, and React

By : Dmitry Sheiko
Book Image

Cross-platform Desktop Application Development: Electron, Node, NW.js, and React

By: Dmitry Sheiko

Overview of this book

Building and maintaining cross-platform desktop applications with native languages isn’t a trivial task. Since it’s hard to simulate on a foreign platform, packaging and distribution can be quite platform-specific and testing cross-platform apps is pretty complicated.In such scenarios, web technologies such as HTML5 and JavaScript can be your lifesaver. HTML5 desktop applications can be distributed across different platforms (Window, MacOS, and Linux) without any modifications to the code. The book starts with a walk-through on building a simple file explorer from scratch powered by NW.JS. So you will practice the most exciting features of bleeding edge CSS and JavaScript. In addition you will learn to use the desktop environment integration API, source code protection, packaging, and auto-updating with NW.JS. As the second application you will build a chat-system example implemented with Electron and React. While developing the chat app, you will get Photonkit. Next, you will create a screen capturer with NW.JS, React, and Redux. Finally, you will examine an RSS-reader built with TypeScript, React, Redux, and Electron. Generic UI components will be reused from the React MDL library. By the end of the book, you will have built four desktop apps. You will have covered everything from planning, designing, and development to the enhancement, testing, and delivery of these apps.
Table of Contents (9 chapters)

Tooling Redux

In Chapter 5, Creating a Screen Capturer with NW.js, React and Redux Planning, Design and Development, you have learned the essentials of the Redux state container. We built a functional prototype using Redux. However, when building your own application, you may need to know when and what is happening to the state tree exactly.

Fortunately, Redux accepts middleware modules to deal with cross-cutting concerns. The concept is pretty similar to the one of the Express framework. We can extend Redux by hooking third-party modules on the event when an action gets dispatched but hasn't yet reached the reducers. It doesn't make much sense to write a custom logger as many are already available (http://bit.ly/2qINXML). For example, for tracing changes in the state tree, we can use the redux-diff-logger module that reports only the state diffs, which makes it much...