Re: [Maya2osg-users] Discussion of next changes

[Jean-Sébastien G. <jea...@cm...>]

Hi guys,

> I notice two camps of interest, but you can proof me wrong. Javier, you
> don't like cluttering the notes field, J-S wants to use as much of maya
> as is available, includeing the notes field, and me, I'd prefere the
> notes field as well.

I think notes is OK, because the things that would be added are clearly 
marked. So the exporter won't touch anything that's not between (as you 
suggest, but could be something else) <osgDescription> ... 
</osgDescription> tags.

In fact, all this started with the fact that Javier doesn't want to 
populate the node descriptions with material properties in the plugin's 
C++ code, so wherever we put it, it will be user-visible. If we could do 
this in the C++ code, it would be transparent to the Maya user (we 
wouldn't clutter the notes, and we wouldn't need attributes, but we 
could also export them if we want to).

I see these things as totally orthogonal. The Maya scene already has all 
the information to put the material properties in the node descriptions, 
so why require that they be put in the notes or an attribute at all? On 
the other hand, if the artist has put notes or attributes, these could 
be part of the exported file as well, nothing prevents that.

What do you think?

J-S
-- 
______________________________________________________
Jean-Sebastien Guay    jea...@cm...
                                http://www.cm-labs.com/
                     http://whitestar02.dyndns-web.com/