Quote - What is it what stops you to use what you like inside your "worker" lib? Look how odf did it. You just have to make sure your output goes to "file". That's all.

Nothing. I'm using odf's geometry worker exactly as it is. I didn't rewrite that.

Quote - Splitting things up insteed of having one monolitic piece of code is required to follow one of the basic ideas: Try to make Poser compatible with other render engines. Not only Lux.

But that's exactly one of the motivations I had for rewriting a bunch of stuff. You have many of the workers in one big file. I have each in a separate file, and all they have in them is stuff that actually exports. There is nothing in them that does any kind of book keeping or parameter gathering. That's all done before they get called by a common class called Exporter.

Furthermore, the Exporter class is not specific to Lux. It is designed to wrap any package of exporters, regardless of what they are for. It will take care of instantiating each module, setting up all the data properties, managing the subfiles, etc. It has nothing whatsoever to do with LuxRender. It only has three parameters to make it work for any target renderer. These parameters are the package name, the exporter name, and the name of the master output file wrapper (in this case, 'lux').

Quote - So the steps: Output one light, output one material, etc. is required if we want to follow the basic requirements. Beside of that, is just a good coding style.

But this is not news. That's how I did it. I don't know what you're getting at here, especially since you haven't seen the code yet.

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)