rs-pbrt-test-scenes VS tealsql

So, I started working on a library to deal with reading data from Blender‘s binary .blend files. In the past I was able to render some Blender v2.79 files, now I abstracted the library to deal (in theory) with all Blender versions (using the DNA information). I tested with two scenes for Blender 2.79 and Blender 3.0 (which should be quiet different from the GUI perspective). With v2.79 I got away with a naming convention and mis-using the old material settings (pre Cycles renderer). Blender 3.0 forced me to get some material settings from shader nodes and the library allows to follow pointers from one data structure to the next. Prove of concept: Both, the Cornell box, as well as the Radiance Conference Room, render with both Blender scene versions. Get the latest Blender scenes here: https://gitlab.com/jdb-walter/rs-pbrt-test-scenes/-/tree/master/blend

A project that uses tealr can be found at https://github.com/lenscas/tealsql/tree/master/pgteal, with online documentation available over at https://lenscas.github.io/tealsql/

There is also https://github.com/lenscas/tealsql which is used as kind of showcase project for tealr and tealr_doc_gen. While at the same time (hopefully) filling a pain point in the lua/teal eco system.

tealsql, my sql library for lua: Right now, it is being used to dog feed the changes in tealr. So, mostly improving its documentation, and preparing it to release it.

last weekend I put in some more time in tealsql, a postgresql client written in Rust for lua/teal.

The main focus is my sql client for teal/lua https://github.com/lenscas/tealsql , mainly getting rid of every part in the api that doesn't have a good type yet on the teal side of things (any, {any:any}, etc.

tealsql, an sql client for teal/lua. Current plan is to get the async api finished (right now it ignores every error but otherwise works without problems).