-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
File extensions for external shaders #738
Comments
I wasn't aware that a reasonable convention existed here - I've seen The recommendation to use Related: http://stackoverflow.com/q/6432838 |
Is this really worth the change? Should glslang integration really drive us to change this when after dozens of implementations, this has not been a concern? We are making fixes for 1.0.1, but we have to be careful that we just don't put every arbitrary change on the table. |
|
Is it worth discussing this as part of KHR_technique_webgl? |
Yeah, we should also ensure that shader sources could be loaded from bufferViews. |
It's been decided that shader files can have any extension. |
While it's not required to use any specific filename extension for shader files, could we recommend usage of
.frag
/.vert
instead of.glsl
?This could simplify pipeline integration with glslang.
The text was updated successfully, but these errors were encountered: