I create this task here so we can talk about a design/implementation for a decent API and improvements for Cycles standalone.
Image: [[ http://blender.dingto.org/cycles_standalone/standalone_examples.png | The Cycles standalone app ]]
Standalone code: https://developer.blender.org/diffusion/B/browse/master/intern/cycles/app/
At the moment we have a basic xml api, which was only intended for testing.
Examples can be found here: http://blender.dingto.org/cycles_standalone/Cycles_Standalone_Examples.zip
I think we need an api which is easier to read/write, while still staying simple and manually editable.
We'd like to get feedback from people, who are interested in integrating Cycles into other applications.
**Reasons to make this happen**
I still see a great potential in the standalone, and as most code is already there, it shouldn't be too hard to make this usable.
- Cycles would become usable for other 3D applications, and therefore we could also get more potential developers. I had one inquiry from someone who wanted to write a Maya exporter, but due to compile issues and the API story, it didn't work out.
- Even for Blender, it would help as benchmark and testing tool for the engine itself. We could have a automated test suite then.