An Initial Visualization Interface
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 27
- Forks
- 11
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 23
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with related issue #490 and inventory the existing unofficial case/model visualization tools. Compare the proposed ./GridKit/Render/ boundary with ./GridKit/Model/, then assess the WebGL/WebGPU direction and available .wgsl shaders. Done means an agreed location and scope for a domain-agnostic visualization interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100