Cool, yes, practical, maybe. By the looks of it, it sounds like your setting yourself up with required maintenance, as opposed to optional maintenance. This could potentially be dangerous; the difference between the two is that, without you or someone else to maintain such a system, no one will be able to perform any work. Worse yet, if this system fails or lacks in any way, everyone will be affected until it is either fixed or replaced.
Difficult to say without specifics, both in terms of usage and implementation. Context the is most important I think. If you were at Weta, complexity at this level (i.e. the file-organisational level) would be more likely to fly as there would be more personnel to do maintenance. But if you're at a 5-10 man shop, I'd suggest that you evaluate where you see gain, and where you see issues and try and weight them against each other. -- 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/CAFRtmOA4bJhB6ndndrK5Bku4CZEDr6FoFqkhmK6%2BYrf9w564MA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
