I do disagree with you about OOP vs. strings (maya.cmds). You can translate your python skills to other forms of python if you understand the OOP methodology and take advantage of oodles of modules out there — all using the OOP methodology.
Not sure we’re understanding each other very well here, maybe it is a language issue. To try and summarise my opinion, I think PyMEL is great for certain things and less great for others. For the things I do with Python within Maya, I haven’t found it as useful as others might. It sounds like it works very well for the things that you do, or possibly to the way that you work, and that’s great. However it also sounds like you are saying PyMEL, or Object-Oriented Programming for that matter, is the solution to any problem. Is this what you meant? Hi guys - Paul here, I’m one of the founders of Fabric (previously at Softimage and Autodesk). Someone pinged me a link to this conversation and asked if I could contribute. I hope I’m not intruding. A tad off-topic yes. I’d be happy to respond in a separate thread. On 7 July 2014 18:45, Geordie Martinez <[email protected]> wrote: > I look forward to seeing how these new wrappers pan out. But they are just > wrappers like pymel. They'll encounter the same under-the-hood issues and > have to find some way to deal with them. > Pymel has had years of development and is accepted by Autodesk. And I'm > sure there will be similarities and overlap and compromises. > > I do disagree with you about OOP vs. strings (maya.cmds). You can > translate your python skills to other forms of python if you understand the > OOP methodology and take advantage of oodles of modules out there -- all > using the OOP methodology. having a string reperesent an object in 3D > space, itself an object-oriented world, also makes little sense to me. > > I've spent years using pymel and I much prefer it to maya.cmds. (it has > maya.cmds inside so if I had to use it I could). > Especially for getting and setting attributes, connecfting attributes, > dealing with skin clusters, all rigging procedurals, shaders, and file > system importing and exporting, it has the path and glob functions built > in, references, namespaces... Pymel is powerful. As a creature TD I can't > agree with your disagreement. It is very useful. > > Anyway, to each his own. > > > > > > > > On Mon, Jul 7, 2014 at 10:10 AM, Marcus Ottosson <[email protected]> > wrote: > >> I'm certainly not one to argue the merits of object-oriented programming. >> But OOP is only one of many programming paradigms >> <http://en.wikipedia.org/wiki/Programming_paradigm> and is as much of a >> silver-bullet as any other. If you're suggesting it fits and problem I'd >> have to disagree with you; it certainly isn't the only way to go and is >> very much dependent on the problem at hand. The problem in this case being >> commands being wrapped up into objects with methods when what really should >> happen is the Python API being object-oriented to begin with, or at least >> wrapped up into one. Maybe this is what Red9 or MRV is doing, I'm not sure, >> but for anyone looking for OOP in Maya that would seem the more consistent >> way to go. >> >> >> On 7 July 2014 17:41, Geordie Martinez <[email protected]> wrote: >> >>> Getting back to Pymel. I love it. OOP is the way to go. the only way to >>> go. >>> I just hate that it has "mel" in the name. >>> >>> if and when there is ever a concerted effort by Autodesk to truly OOP >>> their Maya python API I will adopt it. >>> but in the meantime. Objects with methods makes more sense than flinging >>> strings everywhere. >>> >>> 2 cents. >>> >>> >>> On Mon, Jul 7, 2014 at 5:13 AM, Christopher Crouzet < >>> [email protected]> wrote: >>> >>>> SideFX came up with Houdini Engine which is a similar idea but not as >>>> complete I guess? Just throwing a prejudice here, not sure what I'm talking >>>> about. >>>> Anyways, I disagree when you say those companies would be against it. >>>> Fabric can act like a glue between them all, potentially bringing more >>>> customers to some of them, and definitely bringing more power to them all >>>> with the crazy optimizations Fabric comes with. >>>> >>>> OT: not sure where you got that I'm inundated with work, I've ben >>>> travelling for over 1 year :D >>>> >>>> >>>> >>>> On 7 July 2014 00:36, Jeremy YeoKhoo <[email protected]> wrote: >>>> >>>>> Ill try my best to look into FabricEngine, and get back to this Forum! >>>>> Like Christopher, I am currently inundated with work, and Fabric is on my >>>>> lower priority list. Also thanks for the info regarding Julia. >>>>> >>>>> From my current knowledge of FabricEngine and Maya, current version of >>>>> Maya have a few internal issues with the API that is causing a few bugs to >>>>> prop up. Additionally I wouldnt be surprised that Autodesk, Foundry, >>>>> SideFX >>>>> and etc are probably against the idea of a middleware platform. So I might >>>>> just wait a bit. >>>>> >>>>> >>>>> >>>>> On Friday, 4 July 2014 12:06:52 UTC+10, Jeremy YeoKhoo wrote: >>>>> >>>>>> Hey guys, >>>>>> >>>>>> I want to ask your personal opinion of pyMel. After reading the topic >>>>>> on Monkey Patching the Maya API >>>>>> <http://christophercrouzet.com/blog/post/2014/06/23/From-Monkey-Patching-the-Maya-Python-API-to-Gorilla-and-Bananas> >>>>>> by Christopher Crouzet and an earlier discussion regarding this topic in >>>>>> this forum >>>>>> <https://groups.google.com/forum/#!topic/python_inside_maya/cLdkFBAgRtI> >>>>>> , I started thinking back to pyMel and wondered if it might be an >>>>>> answer, I feel like kicking myself for disregarding PyMel previously. I >>>>>> have just realised how pythonic and how pyMel holds more of a object >>>>>> oriented paradigm as opposed to MEL and maya.cmds (even described by >>>>>> Autodesk >>>>>> <http://download.autodesk.com/us/maya/2011help/PyMel/why_pymel.html>) >>>>>> >>>>>> >>>>>> So I have a few queries, Pymel is now being shipped with Maya, but >>>>>> not supported by Autodesk which my have production implications. >>>>>> >>>>>> What do you guys think of Pymel? >>>>>> >>>>>> -Jeremy >>>>>> >>>>>> >>>>>> -- >>>>> 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/9de94ba1-2607-46d5-82ee-4bcad3fd6067%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/python_inside_maya/9de94ba1-2607-46d5-82ee-4bcad3fd6067%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> >>>> -- >>>> Christopher Crouzet >>>> *http://christophercrouzet.com* <http://christophercrouzet.com> >>>> >>>> -- >>>> 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/CANuKW52_ij1KZ50ztmpazooR_9hJV34sphsAGSd9hULUNfa%3DWg%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/python_inside_maya/CANuKW52_ij1KZ50ztmpazooR_9hJV34sphsAGSd9hULUNfa%3DWg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> 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/CABPXW4geLsbG4%3DjGqMP6PHk%2Bk3g6GtK9SjRihq5oQ3Dc8F%2BTmw%40mail.gmail.com >>> <https://groups.google.com/d/msgid/python_inside_maya/CABPXW4geLsbG4%3DjGqMP6PHk%2Bk3g6GtK9SjRihq5oQ3Dc8F%2BTmw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> *Marcus Ottosson* >> [email protected] >> >> -- >> 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/CAFRtmOAg%3D_v6CWPyG91Q2kQ_V-npQBvAFEPz8qdSBLWPUhpDmA%40mail.gmail.com >> <https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOAg%3D_v6CWPyG91Q2kQ_V-npQBvAFEPz8qdSBLWPUhpDmA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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/CABPXW4iFB-cpt-Y1Nb%2B6QMQHztOwmDqSF0fSJq_dk%3DhQE7e9cw%40mail.gmail.com > <https://groups.google.com/d/msgid/python_inside_maya/CABPXW4iFB-cpt-Y1Nb%2B6QMQHztOwmDqSF0fSJq_dk%3DhQE7e9cw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- *Marcus Ottosson* [email protected] -- 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/CAFRtmOAVS1hbdWH7YWtK4rcA3kNVtxrt9N1fTZtpoOke877MQA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
