-
Notifications
You must be signed in to change notification settings - Fork 1
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
default shaders #1
Comments
According to
Meaning this would require a documentation change to azul3d/gfx -- which is okay, but for backwards compatibility guarantees we have to bump the version number up (silly for just this one thing). Upon more thought into this issue -- the real truth is that:
See new issue for this at azul3d/examples#4 |
I think that's a fine idea, plus many editors support glsl files. Maybe another idea for an example is dynamic reloading of a shader file via fsnotify. It's actually kind of a touchy subject reloading a shader file depending on the editor used and how it "saves" a file, but the code isn't overly verbose and for someone learning shaders, having a way to edit the glsl file and see those changes immediately while running the program is a great learning tool. |
Very interesting idea! Please create an issue for that at azul3d/issues as I would like to see that feature somewhere too, or even hear other's thoughts on it. |
It would be nice if renderers could provide default shaders that work for most generic cases. The default shader should try to encapsulate all current examples such that no shader is needed.
This issue is a complaint from a user about not being able to use the graphics engine without explicitly writing GLSL shaders.
The text was updated successfully, but these errors were encountered: