A <COLLADA> element contains a bunch of lists of <library_*> elements.
Apparently there is no order defined on those <library_*> elements - is this correct? This would imho somehow defeat the support for SAX-style parsing since it means that potentially *every* read data has to be kept in memory. (Ok, I could write read data out in another file format but...)
So, is the following (pseudo) code orderwise correct or is there some constraint on the order in some specification I haven't found yet?
The problem here is that even after instantiating the geometry its instances are still incomplete - they lack the "real" materials, which are finally defined much later on.Code :<COLLADA> <asset/> <library_geometries> <geometry id="cube"> ... <polygons ... material="cube_mat"> ... </geometry> </library_geometries> <library_nodes> <node id="node"> <instance_geometry url="#cube"> <bind_material> ... <instance_material symbol="cube_mat" target="still_to_come"> </bind_material> </instance_geometry> </node> <library_nodes> <library_materials> <material id="still_to_come">...</material> </library_materials> <library_effects>...</library_effects> ... </COLLADA>
Thanks for any hints