Comments on: Making Maya’s Python palatable http://porg.es/blog/making-mayas-python-palatable Tue, 27 Dec 2011 14:16:55 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Porges http://porg.es/blog/making-mayas-python-palatable/comment-page-1#comment-140906 Porges Sun, 09 Aug 2009 09:59:07 +0000 http://porg.es/blog/?p=300#comment-140906 Yes, I never meant it to be more than an easier, or 'more natural' syntax-hack for those coming from Python. That's why I named it "Wrapper"! :) For what it's worth, I ended up extending this to be a little bit smarter... for one thing this short example only affects the first object in the array returned by <code>cmds.sphere</code>. However, I don't seem to have kept it (I just cooked it up for a short Uni project). Thanks for your comments :) Yes, I never meant it to be more than an easier, or ‘more natural’ syntax-hack for those coming from Python. That’s why I named it “Wrapper”!

For what it’s worth, I ended up extending this to be a little bit smarter… for one thing this short example only affects the first object in the array returned by cmds.sphere. However, I don’t seem to have kept it (I just cooked it up for a short Uni project).

Thanks for your comments

]]> By: Rob T. http://porg.es/blog/making-mayas-python-palatable/comment-page-1#comment-140658 Rob T. Fri, 07 Aug 2009 22:10:53 +0000 http://porg.es/blog/?p=300#comment-140658 Nice trick, but your comparison is not really fair. Your negative example is using the "sphere" command to get and set the radius attribute. Then, your code is little more than a string substitution into the setAttr and getAttr commands. Nice use of Python, by the way, but not a substitution for the "sphere" command. The actual Maya.cmds example that you are addressing is: <pre>s = cmds.sphere() r = cmds.getAttr( '%s.radius'%(s) ) cmds.setAttr( '%s.radius'%(s), 10 )</pre> I'm not criticizing your skills <em>at all</em>. I've just had to diffuse a few viral e-mail threads at my studio claiming your Wrapper class is some sort of object-oriented Maya.cmds wrapper, when it only wraps setAttr and getAttr. Nice trick, but your comparison is not really fair. Your negative example is using the “sphere” command to get and set the radius attribute. Then, your code is little more than a string substitution into the setAttr and getAttr commands. Nice use of Python, by the way, but not a substitution for the “sphere” command. The actual Maya.cmds example that you are addressing is:

s = cmds.sphere()
r = cmds.getAttr( '%s.radius'%(s) )
cmds.setAttr( '%s.radius'%(s), 10 )

I’m not criticizing your skills at all. I’ve just had to diffuse a few viral e-mail threads at my studio claiming your Wrapper class is some sort of object-oriented Maya.cmds wrapper, when it only wraps setAttr and getAttr.

]]>