What do you think about modelling the primitives involved using something like http://www.jointjs.com/api ?
I envision reactive modelling systems that can present the primitives to allow users to build valid reactivity models where the systems would map the primitives to domain specific object representations during designing and environment specific implementations during manifestation (provisioning/deployment).
I think I can build my whole system on these primitives (plus a few more) and am exploring ways to passively and actively visualize the processing nodes and data flows. It should be possible through static analysis and sufficient meta data to generate all meta data needed to drive such visualizations to represent a system. Most important in such a visualization system is to ensure you have fallback primitives for anything legacy that does not quite fit the new new model but can be shimmed to avoid a break in the flow.
Anyway, I am interested in exploring this further if you think it has legs. We can call the project gvorGeneral Visualization of Reactivity and build up a library of modelling primitives and specs that can be loaded into IDEs.
I am going to build a visualization system to handle something like this. It will be canvas D3.js based and when I get around to it I will be looking to build a pluginset for gtor.
What do you think about modelling the primitives involved using something like http://www.jointjs.com/api ?
I envision reactive modelling systems that can present the primitives to allow users to build valid reactivity models where the systems would map the primitives to domain specific object representations during designing and environment specific implementations during manifestation (provisioning/deployment).
I think I can build my whole system on these primitives (plus a few more) and am exploring ways to passively and actively visualize the processing nodes and data flows. It should be possible through static analysis and sufficient meta data to generate all meta data needed to drive such visualizations to represent a system. Most important in such a visualization system is to ensure you have fallback primitives for anything legacy that does not quite fit the new new model but can be shimmed to avoid a break in the flow.
Anyway, I am interested in exploring this further if you think it has legs. We can call the project
gvor
General Visualization of Reactivity and build up a library of modelling primitives and specs that can be loaded into IDEs.