> > But what exactly would become published? > > For example, if I work on animation for shot 5000 of The Avengers, and I > save my scene as `my_scene.mb`, alongside other files named equally poor > but differently, would publishing this shot mean to publish the.. > > A) ..latest modified one? > B) ..the one with the highest number (if any; possibly version number)? > C) ..all files? >
That's upto your pipeline, which file you wanna pick. If you are keeping a naming convention for your files, then you can go for the latest version, or else you have to specify the file name. It seems to me that publishing would require at least one more level of > specificity, which in this case would be the actual file. One more if also > specifying what portion of a file to publish, such as Mesh A, but not Mesh > B. > In these cases we should need more details about the file. What we used to do is, we used to keep a *package info file*(a json file) for storing all information related to the file. and allowed artist to publish in two way, 1. internal(wip) - which is not shared among different disciplines, it's just local to them(department). 2. Release - Which is actual publish and shared among different disciplines. So, the publish tool take this package file in-order to publish which is having a proper naming convention, and it is mandatory to have one in-order to publish your file. The CLI option to publish should be another way of doing your publish other than from your host application. In that case an artist who finish their work one day and come next day, then he need not to open the host application for doing only a publish. it can be done through CLI is well. Thanks Liju K On Thursday, 9 July 2015 11:57:24 UTC+5:30, Marcus Ottosson wrote: > > But what exactly would become published? > > For example, if I work on animation for shot 5000 of The Avengers, and I > save my scene as `my_scene.mb`, alongside other files named equally poor > but differently, would publishing this shot mean to publish the.. > > A) ..latest modified one? > B) ..the one with the highest number (if any; possibly version number)? > C) ..all files? > > It seems to me that publishing would require at least one more level of > specificity, which in this case would be the actual file. One more if also > specifying what portion of a file to publish, such as Mesh A, but not Mesh > B. > > It sounds like a really good and flexible idea that I'd like to implement, > but technically I'm having trouble coming up with a non-ambiguous path for > it. > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/e47f1621-430d-424b-9b8c-81450730c092%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
