Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the names of the uniforms used by p5.js to the shader documentation #6286

Open
3 of 17 tasks
RandomGamingDev opened this issue Jul 25, 2023 · 2 comments
Open
3 of 17 tasks

Comments

@RandomGamingDev
Copy link
Contributor

Increasing Access

This would allow people creating shaders to better and more easily work with the p5.js framework.

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 enhancement details

For instance with colors and the matrices needed for 3d rendering, this would be really great for people who want to use the p5.js versions.
The list of uniforms would be added to https://p5js.org/learn/getting-started-in-webgl-shaders.html.

@nandini584
Copy link

Hey @RandomGamingDev I want to work on this issue, could you give me more insight on this?

@RandomGamingDev
Copy link
Contributor Author

@nandini584 There's no list containing the names of all of the uniforms for p5.js currently, the closest thing that I've found is https://github.com/processing/p5.js/blob/main/contributor_docs/webgl_mode_architecture.md#shader-parameters. This would be used for easy interoperability with vanilla p5.js shaders and APIs in general. For instance, if someone wanted to work with a certain noise effect, but add a bit of extra code on top of it to work alongside some other stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Documentation
Development

No branches or pull requests

2 participants