prototype test viewer

[mighdoll]

I realized that many of the image regression tests for Lygia also work as demos. It's not surprising, I suppose, even though I didn't figure it out right away. After all, the wesl-test API is similar to the glslViewer. And of course WebGPU and wesl-js are designed for the browser. So I made a little prototype web app to view the tests. Visit toyviewer.pages.dev, and select the Lygia package.

Lots of things might be done with a web hosted viewer, but which ones are the most interesting? Maybe it gives you some ideas?

[patriciogonzalezvivo]

@mighdoll this is great! Would you be interested in adding a wesl shader editor to lygia.xyz in the same way we do for glsl? Forex: https://lygia.xyz/draw/fill ?

[mighdoll]

Whoa, I hadn't seen those! We should definitely do something editable like that! Where are those configured? links to book of shaders, overlay value sliders! what else am I missing? (oops maybe I clicked too much: {"error":"429 Too Many Requests: 100 per 1 minute"})

[patriciogonzalezvivo]

@mighdoll Sending you an invitation to the repository with the code running on the server.
That code have 3 main purposes:

1. Be an https server for https://lygia.xyz documentation pages. As part of that pics the examples from the shaders headers and displays them on a online editor.
2. Resolve dependencies and stream them back with all internal dependencies satisfy. So if someone ask for a file like 'lygia/color/luma.glsl' it resolves the dependency to lygia/color/spaces/rgb2luma.glsl and return it all together as a single text.
3. Render the members of license by checking github's repo for contributors and sponsors.

[mighdoll]

@mighdoll this is great! Would you be interested in adding a wesl shader editor to lygia.xyz in the same way we do for glsl? Forex: https://lygia.xyz/draw/fill ?

working a bit today on creating a component that can run examples like this. The rough idea is to have a <wgsl-play> component to show runnable examples. Eventually also a <wgsl-edit> component to show source code. Aiming to be web framework agnostic.

I figured those two components ought to be usable independently of each other. And maybe it'll make sense to have some kind of -doc component that combines -play and -edit and maybe more things. Not sure what's best yet, but will share bits as I have them.