Indeed, about 10 years. But I didn't do a public release until a few months later. I really, really do hope to do reframe2 at some point when things get less busy. Just a few key tweaks
Took signaal/re-signaali into use in a React Native application that uses UIx, early days, but seems to work π
This is very cool. From the perspective of a owner of a codebase with UIX and re-frame, having the reactivity not depend on reagent is a huge win. Canβt wait to try either re-frame signaali or re-frame 2
@mikethompson Here is my fork of Re-frame which is using Signaali for the reactivity and UIx as the React wrapper: https://github.com/metosin/re-signaali
From the user's perspective, this fork is useful because: β’ It avoids the jumping caret problem with the input HTML elements and its equivalent in all third party components. β’ Signaali was designed specially to avoid reactivity glitches. All the derived reactive nodes and effects are re-run exactly once and always in the right order. β’ Signaali's source code is (subjectively) easier to read that the reactivity source code in Reagent.
Would you still target Reagent or a more modern React binding? (or all of them?)
I made a CLJC reactive library which is almost ready for release, and I also made a fork of Re-frame 1.4.3 to make it use it. Let me know if you want my input or review for Re-frame2's reactivity integration. I would gladly assist.
I'd certainly consider alternatives. The reactive part of reframe2 won't be based on ratoms.