-
Notifications
You must be signed in to change notification settings - Fork 18
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
template and guide to writing first shaders #77
Comments
I'm curious where you'd want to set up the shader deving environment. Add an option in recur to start glslviewer mode on the pi so you could connect a USB keyboard and develop from there? |
@sebiik , yeah - i was thinking basically some instructions on how to edit a shader on the pi, (probably dont need a option to start glslviewer from within recur at first although that would be cool!),
do you have any ideas on how to ease the entry for people customising there own video-effects etc ? |
If using ssh #110 works well; One thing about just using glslViewer is that you have to supply something for the (midi) param values or else a lot of the shaders won't really work. By being connected to the pi, I can use my own editing environment on a different machine (and even use glslViewer there as a single-shader preview, though there is still the param values problem) and get good live feedback for learning, especially helpful with the 2-input shaders which I don't even know how to create with glslViewer or anything else. I will make a special effort to document my learning and if it works out I can put together some documentation about editing environment, ssh setup, glsl, whatever. There is already a bit of documentation and templating here: |
On this angle, I added these (discussed in #152 )
While working on these I also:
Feel free to use these here (let me know, and I will make a PR for shaders.) |
this is partially already documented in conjur repo , but might be a bit highlevel for someone interested in writing their first shader, it should include:
The text was updated successfully, but these errors were encountered: