Quote -
Object: Put some things in (materialname and a pointer to a Poser geometry here), pull the trigger and get someting out (converted geometry ready to use with Lux).

Ah, I see. I was going to suggest that the class or method responsible for exporting the geometry receives an argument "materialHandler" which would respond to a method "emitMaterial". For testing, I would use a very simple materialHandler object, later to be replaced by the real thing.

Another question that occurred to me is how to emit the Lux instructions. There are at least two modi: write to a file or call the Python API. At some later point, we might want to build up an internal data structure that can be manipulated in place before it is passed on to Lux. So I guess it would be good to define an interface for that as well, and pass an emitter object around to which all the output tasks are delegated.

Sound good so far?

-- I'm not mad at you, just Westphalian.