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

Design plugin mechanism #17

Open
zokrezyl opened this issue Jun 2, 2020 · 0 comments
Open

Design plugin mechanism #17

zokrezyl opened this issue Jun 2, 2020 · 0 comments

Comments

@zokrezyl
Copy link
Owner

zokrezyl commented Jun 2, 2020

Though with a risk of bloat, it may make sense to design/implement a plugin mechanism that would allow the injection of different variables (attributes/uniforms) into the shaders, for instance:

  • You may want to visualise a shader on the terminal that is consuming Jack Audio (or any other audio) samples and displaying the FFT or the waves itself
  • You may want to visualise different resource usage (CPU, memory, etc)

This data could be obviously made available through the existing mechanism, but this would mean that the client program would need to run continuously to feed the data and would put the burden of implementing the source of data on the client side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant