This is always a tough one trying to integrate the art people, and forcing them use different open and release functions, not just technically ;)
You could look at the blur studio tools they have an photoshop integration as well if i remember correct. How we did it once, was to send commands through a com interface to photoshop. Here is a blog entry of someone doing it: http://peterhanshawart.blogspot.de/2012/05/python-and-photoshop-code-snippets.html?m=1 Hope it helps you as a start :) -- Sascha Kremers Gesendet mit Sparrow (http://www.sparrowmailapp.com/?sig) On Thursday, 17. October 2013 at 04:46, Panupat Chongstitwattana wrote: > Hi everyone. I need some advice and would appreciate any suggestion. > > On the 3D side, since Maya/Nuke can run Python, I don't have much problem > having Python took care of most stuff from file location, version tracking to > naming convention. > > But how would I go about enforcing similar system to the art department using > Photoshop/Sai/Painter and various other apps? How is it usually done in > production pipeline? > -- > 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/7978b20e-64ca-4200-ab10-e93e0ded2916%40googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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/886E06128B6546BFBF0161E4DB1124AB%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
