Summary
Where is a healthy and standard location to place visualization tools in a modern project? (Related to #490)
Rationale
We have a few unofficial tools to visaulize and render 'cases' or 'models' and it is worth a discussion as to how to partion visualziation from modeling. As GridKit is designed to be domain agnostic in general, its important that visualization be domain agnostic as well.
Description
With a background in game engines, I am partial to the renderer and controller paradigm. The controller is what we would call our Model, thus I initially propsoe we reserve ./GridKit/Render/ for this purpose to complement ./GridKit/Model/
Additional information
Regardnig shaders:
- Broadest coverage:
WebGL
- Future-focused:
WebGPU
WebGPU would be ideal for scalability as we can fully leverage GPU buffers from the browser but WebGL is widely adopted on almsot every device.
I do have some initial .wgsl shaders available for this purpose.
Summary
Where is a healthy and standard location to place visualization tools in a modern project? (Related to #490)
Rationale
We have a few unofficial tools to visaulize and render 'cases' or 'models' and it is worth a discussion as to how to partion visualziation from modeling. As GridKit is designed to be domain agnostic in general, its important that visualization be domain agnostic as well.
Description
With a background in game engines, I am partial to the
rendererandcontrollerparadigm. Thecontrolleris what we would call ourModel, thus I initially propsoe we reserve./GridKit/Render/for this purpose to complement./GridKit/Model/Additional information
Regardnig shaders:
WebGLWebGPUWebGPUwould be ideal for scalability as we can fully leverage GPU buffers from the browser butWebGLis widely adopted on almsot every device.I do have some initial
.wgslshaders available for this purpose.