Adding WebGL texture types
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24k
- Forks
- 3.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 25
Description
Increasing Access
p5.js's addition of shaders meant that a lot more was possible with the library, but the lack of precise texture control means that people either have to waste memory, speed, or themselves poke into the WebGL and p5.js code to get all the data needed for creating more specific textures. For example, if someone wanted 1d or 3d textures, or if they wanted to use UNSIGNED_BYTE textures.
Most appropriate sub-area of p5.js?
- Accessibility
- Color
- Core/Environment/Rendering
- Data
- DOM
- Events
- Image
- IO
- Math
- Typography
- Utilities
- WebGL
- Build Process
- Unit Testing
- Internalization
- Friendly Errors
- Other (specify if possible)
Feature request details
Give a function similar to the createImage function for WebGL only that gives control over the WebGL parameters of the texture while also working with the other parts of the p5 library.
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 createImage API and the WebGL rendering area described in the issue. Define what texture parameters and texture types need to be exposed, then verify that the new function works with the other p5.js APIs and supports the requested 1D, 3D, and UNSIGNED_BYTE texture use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100