WebAssembly / WebAssembly/wasi-webgpu
frame-buffer.buffer needs dimensions, stride, and pixel layout (e.g. RGBA/BGRA)
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 220
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
frame-buffer.buffer needs dimensions, stride, and pixel layout (e.g. RGBA/BGRA) so programs know what the bytes mean, how big a pixel is, how big a line of pixels is (width and stride), etc.
Contributor guide
No contributing guide indexed for this repository
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 by locating the frame-buffer.buffer API definition referenced in the issue. Determine how dimensions, stride, pixel layout, and pixel size should be represented; the work is done when programs can interpret the buffer bytes unambiguously.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- api, computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100