A while ago I released the new version ReduxFX 0.2. For this release, I completely rewrote the view-builder API to make it more “IDE-friendly”. In addition, ReduxFX now supports applications with several windows.
Recently we have founded a new Java User Group in my home town, the JUG Freiburg. If you happen to be in the area, we would be happy to welcome you in one of our meetings – either as an attendee or to give a talk yourself.
As mentioned in my previous post, I added two important new features to ReduxFX 0.1. While the previous post focused on the ability to communicate with the outside world from ReduxFX application, this post focuses on the second new feature: the ability to write standard JavaFX components.
Last week I released version 0.1 of ReduxFX, which added two important features to the library. Now ReduxFX has support for the development of UI-components and it is possible to communicate with external systems. In this post I will give a short introduction into the latter.
The first part of this series gave an overview of the key concepts and listed some of the main advantages of using functional reactive programming techniques in UI development. Future articles we will focus on different components that are involved, starting today with the State component, a key ingredient of functional reactive UI programming.
React.js, Elm, Cycle.js, and other UI frameworks introduced a new way of building user interfaces. By applying principles from functional reactive programming to UI development, they even changed how we think about user interfaces. In no time, these approaches have simply smashed the seemingly inevitable dominance of MVC and its siblings (MVP, MVVM etc.). This article, which is the first in a series, will give a brief introduction into this new way of building UIs and list some of the advantages it has over traditional approaches. These factors are so strong, that in my opinion there is a good chance that we are right now witnessing the end of the MVC-era.