From my point of view, Flash/AIR is a no go. If we want to have flexibility, we can open a Browser-Window, show a page made with Javascript and put the results to the Exporter. I did a "HTML-Formular-Getter" for Poser years ago already. It's pretty easy and works fine with all versions.

On the other side: Using things we have in Poser and what works without problems/additional know-how is the best we can do yet. There is a bigger chance others grab the code and make some usefull things. Without being a specialist or a need to study the source code for month beforehand.

If we want to involve something other than Poser (Flash/AIR) we better create a "man in the middle" (between Lux and Poser). Sort of a General exporter able to deal with several "geom-handlers" to get data and put them out to a render-engine (Lux, whatever). But things like this are a step to far.

For the moment I think its better to keep things as simple as possible (program structure), so anybody with a little bit of Python know-how is able to jump in and resolve an isolated problem. Or add a feature. Or things like that. Speed is something we can deal with at the very end. Thats pretty easy to do if an object has no "side-effects". Rule of thumb: An object should know and use only objects it has created by themselve. Anything other an object is using should be value-parameters or ready to use results from a global parameter-structure (dictionary).

I understand that bagginsbill wants to get a result as quickly as possible. I for me want to see a "long-living" Project without an "owner" or somebody/something the project depends on (beside of Lux and Poser).

---