wow, I am so glad I asked. It very interesting your points of view, and
very clarifying.
Let me be a little more specific, because that might change some things.
I set my maya environment root to a folder called --> rigbuilder. So this
is just a folder, no package.
Then inside, I have 3 packages: rbguides, rbskeleton and rbsolutions.
Basically I did that because I thought that there are different "themes",
but all being part of the rigbuilder. That is with I started al the folder
with rb
rgguides has inside a module called guides, with a class called Guides too
( I know, it is not beautifull), and the methods called buildArm(),
buildLeg(). All that is to create a primitive locator skeleton reference
that would be the first step.
rbskeleton has inside a module called skeleton, with a class called
BuildSkeleton and no other methods. I called the class BuildSkeleton
because that is what is does. So I would have something like:
import rbskeleton.skeleton as rbs
arm = rbs.BuildSkeleton('....the guides locators arguments here...")
So at this point I have an object arm, that has a lot of attributoes, so I
can do arm.fullDist, arm.side, arm.vectors, arm.campName, arm.segmentsDist
etc...etc... I though it would be interesting because then, I can use all
this data in what is comming. ( That is my approach to OOP, but of course I
will later use polymorphisms, inheritance etc...But I think that creating
an object with usefull data attributes is a good way of using OOP, because
I don´t have to rewrite the same code each time in every functions , and
also, I don´t need to specify the same arguments in the functions. For
instance, if my object as the attribute side ( arm.side), in the rest of
the methods, I just have to write : blablabla = self.side + blalala , so
the method doesn´t have the side argument, because it already knows "what I
am talking about") <<== sorry, I went off on a tangent. This is a
competently different subject
And finally the package rbsolutions that have inside more packages like:
basics, rigs etc... so this package would be the one that , once the
skeleton of the rig is done, will add all the solutions, so each solutions
is a module, such as rigarm.py, legarm.py, legarm_betatest.py, etc, etc...
So as you can see it is a modular rig builder I am working on, that I
structured in the 3 packages. The first one creates the refpoints, the
second creates the skeleton, and the third creates all the solutions for
the rig.
By the way, what do you call the folder that hold the packages. Does it
have a name
thanks
--
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/d00c90e1-8829-49eb-904e-42f0c7a7a85f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
