You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the GLSL code for Megaplot is in large template strings in files under src/lib/shaders. As such, code support tooling such as syntax highlighting rarely works.
Instead, it would be better to have GLSL source code live in files with a .glsl extension. These could be loaded directly in TypeScript via the webpack-glsl-loader plugin, or by some other method.
The text was updated successfully, but these errors were encountered:
Complicating matters: a good amount of the GLSL code for Megaplot is generated (see src/lib/attribute-mapper.ts for example). Any solution should account for these generated fragments.
The generated code currently is generated in the browser on the fly, but it could be generated via a pre-processing step. See util/generate-code.ts for an example of current code generation.
Currently, the GLSL code for Megaplot is in large template strings in files under
src/lib/shaders
. As such, code support tooling such as syntax highlighting rarely works.Instead, it would be better to have GLSL source code live in files with a .glsl extension. These could be loaded directly in TypeScript via the webpack-glsl-loader plugin, or by some other method.
The text was updated successfully, but these errors were encountered: