regl VS threlte

Author of Threlte here 👋 with two cents about Three.js: It's exceptionally well written in terms of rigid and consistent interfaces that allow frameworks such as Threlte to exist to make wrappers/renderers that are as slim as possible. This is due to it being strictly OO but definitely something i would make top priority when creating a new 3D library. Personally I find regl also very interesting with a completely different approach than Babylon or Three.js.

If you go to https://github.com/regl-project/regl , you'll see the last commit was made literally yesterday.

You can create a HTML Canvas with a WebGL context (I suggest using a library like Ogl or Regl )and run the functions exported by this library in a fragment shader, then save the current frame by a method like this or any other.

The author, Mikola Lysenko, is a remarkable engineer. He's wildly prolific, but I my favorite project of his is regl[1], which is an unparalleled WebGL library. I think it might be the best-in-class example of all OpenGL libraries, though I have admittedly fallen behind on the state-of-the-art of desktop OpenGL.

[1] https://github.com/regl-project/regl

bit like regl?

Thanks! I made it with regl: https://github.com/regl-project/regl

Thanks! Threlte is "just" offering a declarative way to express Three.js. If you know how the `` component and its props and event handlers work, you can use the Three.js documentation for everything else.

Apart from that with Threlte I personally practice documentation-driven-development, so ecosystem packages are exhaustively documented. If you're missing something, let us know via an issue[1] or on Discord[2].

Accessibility is a topic we didn't care enough yet to be perfectly honest. Accessibility doesn't stop at screen readers though, it's about contrast, size, colors, motion, reachability, and so much more that we cannot provide and are a consumer topic. Naturally WebGL apps suffer from being practically invisible to screenreaders. There are workarounds[3] but essentially this has to be solved by consumers of Threlte (devs) and hopefully by browser vendors at some point in the future.

[1] https://github.com/threlte/threlte/issues

[2] http://chat.threlte.xyz

[3] https://github.com/pmndrs/react-three-a11y

more specifically it's using the svelte wrapper of three.js called Threlte: https://threlte.xyz/

Three.js is great when there is a layer between me and it's API. Been playing with https://threlte.xyz/ and really enjoying it.

Maybe try https://threlte.xyz/

Now this is a very high level overview and a lot of really important stuff is missing. Things like event propagation, pointermissed events, different event targets, a super clean syntax and more is all implemented in Threlte 6's interactivity plugin. Check out the code here.

GPT-4 is a fantastic tool for coding, really looking forward to using it with the latest Svelte docs. Perhaps consider adding the documentation for Threlte?

) with complex functionality, since the app needed a graphics pipeline and I wanted to write one up myself. The next page I made did not need a pipeline, so I opted to use Threlte (a Svelte version of react-three-fiber) to make the code simpler to write and easier to maintain. If a scene you want to create has a lot of different meshes, materials, animations, etc. you might be best off using Blender to get it looking perfect. You can export from Blender as .gltf files which can be imported into Three. If you want a more specialized solution, I'd need to know your use case a little better. How are you building the scenes?

Hey, awesome work! Check out gltf.report for a quick and easy tool that can resize textures, prune objects and weld/simplify geometry. I’m not sure what Threlte version you’re using, but starting from Threlte 6 which is coming in the next weeks we’re recommending @threlte/gltf for the best possible gltf workflow. Check out our Discord if you need any help!