I should have written it in a more prototype-y way, but I naively built it on something like a custom engine from scratch in opengl :/ (I figured my rendering requirements were specialized enough I should roll my own: after all its just boxes + quads + text)
There's also source available for doing the 'monitoring' side of things in javascript: https://github.com/westoncb/JS-Watcher (though I've been informed since that I might be better off using an existing lib—Immer, I think—rather than writing the stuff to monitor property changes myself.)
Very interesting. From a quick read, I feel like the domain/converter pattern has elements in common with flow based programming, is this close?
I've came another repo that reminded me of some of the goals of your projects, If I get it right. Lava [1], according to the author, it is an architecture to solve "classic software problems" that includes visualization tools.
It's built on top of a simple application framework I wrote largely in order to build Lucidity on top of: https://github.com/westoncb/Domain-slash-Converter
I should have written it in a more prototype-y way, but I naively built it on something like a custom engine from scratch in opengl :/ (I figured my rendering requirements were specialized enough I should roll my own: after all its just boxes + quads + text)
There's also source available for doing the 'monitoring' side of things in javascript: https://github.com/westoncb/JS-Watcher (though I've been informed since that I might be better off using an existing lib—Immer, I think—rather than writing the stuff to monitor property changes myself.)