OK, that's interesting, I haven't worked on any introspective stuff in C++ so I'll look forward on learning more about it
I'm currently looking through the source code of Lux to get a better feel of the program (Later on I'd like to do some work in the Core as I like to do some simulation of some more complex aspects of light (polarization, fluorescence (even possibly phosphorescence (which does not have a great deal of effect in the realism of things, but just for fun, to see how to implement it (I'm a theoretical physicist by education, and do like these weird things
)), dffraction, true sub-surface scattering (I don't actually know if Lux already does SSS?). But as a first education on the workings of Lux I think learning it's input format and API:s are a good way to go. I'm also reading both the ruby and the C/C++ API:s for SketchUp.
While I'm at it, and reading through the code, do you guys want me to do some UML dependency style diagrams and so on for the code? As I'll probably do it anyway for my own understanding so I could do it in a nicer way than pen and paper if you have any use for it?
I have done some personal as well as some work-related stuff with C/C++ API:s in the past (a couple of years ago) so I don't think it should be a problem, the greatest problem is, as always, finding time to do it, but I'll think I can do some 4-8h a week of work on it.