Summary
Support custom WebGPU rendering in bracket-terminal.
Problem to solve
The current WebGPU backend does not appear to provide an easy way to plug in custom WGSL shader-based rendering.
This makes it harder to experiment with custom effects or verify more advanced WebGPU use cases beyond the built-in rendering path.
Proposed solution
Add some form of WebGPU customization support so custom shader-based rendering can be integrated without modifying backend internals each time.
Alternatives considered
- Keep using only the built-in WebGPU rendering path
- Continue testing custom rendering only through the OpenGL backend
Additional context
For example, contributors may want to provide their own WGSL shaders, uniform buffers, textures, and render pipelines without modifying the backend implementation directly.
This would make WebGPU experimentation and validation easier for contributors.
Summary
Support custom WebGPU rendering in
bracket-terminal.Problem to solve
The current WebGPU backend does not appear to provide an easy way to plug in custom WGSL shader-based rendering.
This makes it harder to experiment with custom effects or verify more advanced WebGPU use cases beyond the built-in rendering path.
Proposed solution
Add some form of WebGPU customization support so custom shader-based rendering can be integrated without modifying backend internals each time.
Alternatives considered
Additional context
For example, contributors may want to provide their own WGSL shaders, uniform buffers, textures, and render pipelines without modifying the backend implementation directly.
This would make WebGPU experimentation and validation easier for contributors.