Currently the shaders use Three's ShaderChunk snippets and runtime #include resolution, which makes them unusable outside of Three (without some effort). The uniforms are also defined by Three but it seems like that would be easy enough to integrate into a different rendering strategy.
One option that could maybe be automated would be to have Three.js prepare the shader program and output the shader source code before it's sent to the compiler. Alternately, we could do that once, save the results to the repository, and feed them to a THREE.RawShaderMaterial instead of a ShaderMaterial.
Currently the shaders use Three's ShaderChunk snippets and runtime
#includeresolution, which makes them unusable outside of Three (without some effort). The uniforms are also defined by Three but it seems like that would be easy enough to integrate into a different rendering strategy.One option that could maybe be automated would be to have Three.js prepare the shader program and output the shader source code before it's sent to the compiler. Alternately, we could do that once, save the results to the repository, and feed them to a
THREE.RawShaderMaterialinstead of aShaderMaterial.