Throwing this out into the wild as perhaps someone in the know will give it a read.
I’ve been working with @ncthom’s excellent Blueprint for some projects recently and have been building up various communication mechanisms for communicating app state changes between a C++ data-model and a React/Blueprint UI.
I’ve currently got a system which is somewhere between the
ReactNativeBridgeClient and the
ValueTreeJsonSynchroniser detailed in this marvelous talk on LUMI’s architecture:
There are murmurs in the talk suggesting some of this code may be open sourced or possibly added to JUCE. Is anyone in the know aware if this is still planned to drop? Annoyingly I’d not watched the full talk until after I started building things
I’ve got a system in place but Blueprint and similar technologies are looking very promising so I’d be interested in whether “best-practice” patterns are soon to emerge in the community. Appreciate not everyone uses
juce::ValueTree as their “data-model” architecture (infact I’m not currently) but it’s likely to be one very popular option.
A system which uses JSON Patch as discussed in the above talk (rather than allocating and pushing around
juce::DynamicObject instances to a JS context/engine) could be valuable for many. I’ve plans to implement similar things for use with Blueprint and the like but want to avoid reinventing an already better designed wheel.