Hi Luca, On Wed, May 18, 2011 at 3:24 AM, Luca Vezzadini <[email protected]>wrote: > > About where to place the descriptions and the syntax for them, let's keep > in mind that each description is treated as a separate string, so I'd say > each one must bring all the info it needs. Which now seems to include also > the material ID. So each line should probably be something like (still using > bars for now): > Material_32|Diffuse|Unit_0|myFile.jpg|80 > > It's true we could have quite a bunch of these depending on how many > materials are in your exported file. But if we can't have them on the single > stateset, then to me it would much better to see them all in a single place > rather them spread on various geodes. This could mean we will see a long > section in the beginning of the file that contains ALL the material > definitions for the whole file. The code on our side would just have to get > the root node of the imported file, get all these description and process > them in a single shot. And even for debugging purposes, being able to open > the file and check all the materials at one is easier. > > Bottom line for me is: everything at the root node is better... >
I agree. Since the information is going to be decoupled from the stateset anyway, might as well have it all in once place. Regarding the format, are you suggesting that there should be a single description string that contains information for all the materials? Or each material should still be a separate description, but include the material name on each map entry line? Cheers, Farshid
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
