Hi,
Is it advisable to have a pipeline in python. Will python give all the features and flexibility to make a successful pipeline.
Is it possible to call mel commands from python editor within mayaBRgds,
kNish
in my opinion Python is one of the best thing added to Maya. Python is a wonderfull language, very powerfull and flexible. Although the python documentation is confusing some time ... i am talking about the python doc not the maya python doc.
And yes you can call still call all the mel command in python. all the major mel commands have a python counterpart, and all the mel command not converted in pyhton commands you can call them by using the maya.mel.eval("mell command here") command.
just the fact that I have access to array of arrays is enough for me to use python instead of mel.
QUOTE(Kobayashy @ 05/22/08, 05:51 PM) [snapback]286029[/snapback]
just the fact that I have access to array of arrays is enough for me to use python instead of mel.
Yes but then i really suggest you doing things with the api part of python and not use maya.cmds because then your doing algorithmic code annd thet defeats the purpose of the normal engine.
So i dont really understand the motivation in taking very basic system and putting it on top of a full fledged programming stystem and then on pupose do things with the slower system.
Mind you i dont really see any problem with python and maya. Just see no bigger point in the maya.cmds section of python, since it gets all the idiocies of mel and inherits them making for a even more idiotic system. So in the end you end up blind to the nono's. Theres no bugger point in being able to call then trough python you can still do it trough api.
Anyway theres slightly higher overhead for keeping things up to date. Since the interface is slightly in flux still.
QUOTE
array of arrays
Mel can do arrays of arrays.
the issue of maya.cmds versus maya.OpenMaya (api) is one that has been of great interest to me lately.
QUOTE
Yes but then i really suggest you doing things with the api part of python and not use maya.cmds because then your doing algorithmic code annd thet defeats the purpose of the normal engine....Theres no bugger point in being able to call then trough python you can still do it trough api.
that's kind of like saying that there's no point in writing a function of your own, because you can always use builtin python functions. yes, you can do everything that maya.cmds does using api, but it would be a ridiculous amount of work to replace every mel command with api. after all, under the hood maya.cmds is api code. the primary problem -- aside from the procedural design -- is that maya.cmds is still tied to passing and returning strings instead of maya api objects. opening up maya.cmds to accept MObjects would be a huge step toward integrating these two systems. it would remove the repetitive and unnecessary translation back and forth between maya-readable and human-readable objects for those who know how to use it, while still maintaining the user-friendly string-based interface for quick scripting.
this list of suggested changes to maya.cmds covers this as well as other shortcomings: http://code.google.com/p/pymel/wiki/Autodesk
QUOTE
Anyway theres slightly higher overhead for keeping things up to date. Since the interface is slightly in flux still.
i'm curious what you mean by this. what part of the interface is in flux?
-chad
split this off to because it got a bit out of hand :