voronstl/exercises
2026-03-05 13:53:27 -08:00
..
create_glb_links safety, glbs now have no sanitizing of file names; png & webP conversions work 2026-03-05 13:53:27 -08:00
create_glbs safety, glbs now have no sanitizing of file names; png & webP conversions work 2026-03-05 13:53:27 -08:00
create_manifest safety, glbs now have no sanitizing of file names; png & webP conversions work 2026-03-05 13:53:27 -08:00
create_png_from_glb safety, glbs now have no sanitizing of file names; png & webP conversions work 2026-03-05 13:53:27 -08:00
create_png_profile safety 2026-03-04 17:47:07 -08:00
README.md glb -> PNG works, next is exercise for creating links to all glbs 2026-03-04 18:39:27 -08:00

This project/task is complex in that you have STL files marshalled from various repositories and then need to create derivative glb (glTF binary) versions and then create PNG images from the glb. I have desigend this so that the directory tree paths remain intact which helps identify the file's provenance. This project took several days and I had to winnow out the errors in my back-and-forth sessions with ChatGPT.

Another quirk is that i use Gentoo Linux which often complicates matters. Running this on Raspbian, Debian, or Ubuntu may have some steps such as installing certain packages which I have not accounted for. I've created these exercises to demonstrate and reproducible step so the read has an understanding of what is happening.

This started off as a desire to have more readable images as the 14 pages color printed manual had many of the black shapes undiscernable. I started off with having a 3D rendition which is great and allows me to study a part if I cannot match with what was shipped to me. Then I gave further thought about a printed manifest and the interactive 3D experience cannot be in that form of a deliverable. So, I built upon the glbs and create a workflow that generates PNGs.

One caveat: by placing all the PNGs in one directory, and creating soft links to all the properly staged glbs, I am assuming there will be no name collision. But given that the Voron project consists of many projects, the potential for file name collisions is very real. I leave that as an enhancement if anyone cares to build off this project.