<div dir="ltr">Hi,<div><br></div><div>Reading your doc i'm not really sure, is the actual implementation and maintaining the format / importer is in your plans?</div><div><br></div><div>As for feedback, it's not really clear which exact aspects of current format you consider most problematic and how you're proposing them to solve. The only thing which is currently not met to your requirements is compressed/binary mesh data, but it;s rather simple to integrate into XML.</div><div><br></div><div>I'm also not sure why human-readability should be a requirement. Not saying we should not have human-readable format (in fact, we should have it and default scene examples in repo should be rather in readable and easy to tweak format), but i don't think it's something which should be used in real production environment. Some binary format would solve lots of parsing overhead and possible precision loss during parsing.</div><div><br></div><div>Imo, ideally it should also be some nice plug-in based system for parsing formats.</div><div><br></div><div>Don't get it wrong, i'm really happy there's enthusiastic guy who's jumping into this issue, just giving some preliminary feedback about areas of your proposal which seems to be requiring more work.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 21, 2015 at 2:33 PM, Levon <span dir="ltr"><<a href="mailto:levonh@gmail.com" target="_blank">levonh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Ive been writing down some ideas regarding the Cycles XML format.<div><br></div><div><div><a href="http://wiki.blender.org/index.php/User:Levon/cycles_standalone_format" target="_blank">http://wiki.blender.org/index.php/User:Levon/cycles_standalone_format</a><br></div><div><br></div><div>listing some comparisons between other render engines, and also possible alternative language's.</div><div><br></div><div>I started looking at integrating Cycles into some other 3D Software, and one thing holding me back is not wanting to invest too much time into writing out to the current cycles XML that may not stay.</div><div><br></div><div>While a good Cycles render API would be a great feature, I.m working on defining the .xml (or what ever it becomes) format.</div><div><br></div><div>Ild like to hear some feedback and ideas from other devs and users. </div><div><br></div><div>Im prepared to code it, with input from others.<br></div><div><br></div><div>Thanks :)</div></div></div>
<br>_______________________________________________<br>
Bf-cycles mailing list<br>
<a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-cycles" rel="noreferrer" target="_blank">http://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div><span style="color:rgb(102,102,102)">With best regards, Sergey Sharybin</span></div></div>
</div>