Hi Rudi, Why not pass the stretchy to makeIk as a argument? (i.e. foo.makeIK(stretchy=True) ) same with the method of the twist? adding classes and changing method's names forces the user to import more stuff and learn how to use each one individually, it only adds complexity to your project.
I've said this before, but it looks like you are in your 'subclassing is cool' time (I've been there) so I will repeat the recommendation, please _forget about subclassing_ for now, you are so focused on implementing stuff using classes as categories that it ended up harming your code, all those subclasses are so annoying to maintain and potentially hard to understand (assuming this toy example sets the foundation of a big enough project). Keep it simple, start from the usage code to make sure your interface makes sense, put some effort into testing so you can deliver solutions with some confidence, learn about python types/std-library and use it wisely... all that adds much more value to the quality of your code and generally cannot be done properly as an after thought (but you can always split your classes into subclasses). Said that, I'm not advocating to not subclass ever, all I'm trying to say is don't start layering 'all the things' (tm) just because it's OOP, there are more aspects into it. Cheers! -- 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/CAPamJi8oQh%2BOY3BcxwQw7qc-EQONmr3CzebAUY-6uOyEXXAUxg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
