Generic friendliness?

[Whaat]

While we're talking about exporters. Do you guys know what exporters are already supporting *.igm? ..or how far we are with it?

I have spent the last few nights testing SkIndigo *.igm import and export. I think I have all the bugs squashed now but I am currently not supporting Blend material import/export. I think there needs to be some discussion about how to handle it.
It would be useful for me to download some *.igm files that have been created by the other exporters for testing purposes. Do you have some that you could share, suvakas? I could do the same if you like. This IGM thing is the scariest thing I have ever coded. I had to write my own hack of an XML parser. It will probably cause people's systems to blow up I don't know where the other exporters are at. I hope we can all start sharing materials soon....

[Wedge]

Suvakas: I have no plans on this for the "minimal" exporter I update for Blender. It is something that could be done far easier in a C++ or separate program than to try this from Blender using Python. I am hoping that there are no problems with me ignoring igm.

I would have to open an igm file and search out each line and take the data from it to apply to the different translated material sliders that are being used. (if it is possible to update Blender's interface values by doing this)

So since this "minimal" exporter is already confusing with the translated materials I do not intend to add igm to it.

I write it now with the hopes of its "core" being useful in some way. Further down Indigo's version line I might run out of sliders to translate materials to and then it won't be useful anymore.

[Big Fan]

edited to remove all

[OnoSendai]

Thanks jeffr,
I appreciate all constructive criticism.
A more user-friendly GUI would be nice, but it's a lot of work.
In your particular case, I suggest you try using one of the many exporters for Indigo scenes available.