openframeworks / openframeworks/openFrameworks
feature: Pixel Buffer Object (PBO)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
Just want to propose the idea of implementing a pixel buffer object in openFrameworks.
There are many uses for this - especially if you want to render pixels into vertices - say, using a fragment shader to create points or a mesh.
The PBO could be a new ofPbo class or just adding functionality to the existing ofVbo. The main changes would be:
- Creating non-initialized buffers (unlike setVertexData, that only allows buffers with copy-data), e.g. allocateVertexData(...), alloacteTexCoordData(...), etc.
- Reading pixels into the buffers (from framebuffers), e.g. readPixels(...);
This is a suggestion open for discussion.
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 by reviewing the existing ofVbo functionality, especially setVertexData, and the framebuffer pixel-reading path. The proposal leaves open whether to add an ofPbo class or extend ofVbo, and requests non-initialized buffer allocation plus readPixels support. Done would require an agreed design and working implementation for both capabilities.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100