Queryable transformation stack
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24k
- Forks
- 3.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 25
Description
Increasing access
This would make it easier to get previous and current transformations for things like layer transformations (previously only possible with undocumented methods) on top of one another, which would be great for things like editing programs that could use multiple transformations (e.g. 2d models, 3d art), and it would also help with debugging.
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
- Internationalization
- Friendly errors
- Other (specify if possible)
Feature request details
Create a function that returns a list containing transformation data (could be a list containing the data in any format it shouldn't really make a difference) for each transformation in order (preferrably so that the first/base transformation is at index 0).
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
No file, test, or entry point is named. Start by locating the WebGL/core rendering transformation handling and the undocumented methods referenced in the issue; the work is complete when an agreed function exposes each transformation in order, with the base transformation first.
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
- 35/100