To Do List

To Do in mrv.automation.workflows it would be better to have the createWorkflow method in some sort of workflowManager, for now that appears like overkill though

To Do in mrv.conf.ConfigNode.listSections return an iterator instead

To Do in mrv.conf.Key add support for escpaing comas within quotes - currently it split at comas, no matter what

To Do in mrv.conf.Key.appendValue this implementation could be faster (costing more code)

To Do in mrv.conf.Key.removeValue this implementation could be faster (costing more code)

To Do in mrv.dgfe.GraphNodeBase tests deletion of graphnodes and see whether they are being garbage collected. It should work with the new collector as it can handle cyclic references - these strong cycles we have a lot in this structure. Weakrefs will not work for nested facade nodes as they are tuples not allowing weak refs.

To Do in mrv.enum.Enumeration implement proper pickle __getstate__ and __setstate__ that deal with that problem

To Do in mrv.maya.ns.Namespace.delete Implement undo !

To Do in mrv.maya.ns.Namespace.moveNodes Implement undo !

To Do in mrv.maya.ns.Namespace.rename Implement undo !

To Do in mrv.maya.nt.apipatch.MPlug.moutputs should the method be smarter and deal nicer with complex array or compound plugs ?

To Do in mrv.maya.nt.base.DagNode.duplicate add example for each version of newpath Undo implementation - every undoable operation must in fact be based on strings to really work, all this is far too much - dagNode.duplicate must be undoable by itself duplicate should be completely reimplemented to support all mel options and actually work with meshes and tweaks - the underlying api duplication would still be used of course, as well as connections (to sets) and so on ...

To Do in mrv.maya.nt.base.DagNode.iterInstances add flag to allow iteration of indirect instances as well

To Do in mrv.maya.nt.base.DagNode.parentAtIndex Update dagpath afterwards ! Use dagpaths instead !

To Do in mrv.maya.nt.set.ObjectSet.addMember handle components - currently its only possible when using selection lists

To Do in mrv.maya.nt.set.ShadingEngine Force exclusivity must be a little more elaborate - this could be overwritten and reimplemented to take care of the details

To Do in mrv.maya.nt.storage.StorageBase should self._node be stored as weakref ?

To Do in mrv.maya.nt.storage.StorageBase.copyFrom copy connections to our messages as well, make it an option at least

To Do in mrv.maya.ui.layout.FormLayout.FormConstraint proper constraint system, but could be complicated to make it really easy to use

To Do in mrv.maya.util.Mel.call more docs

To Do in mrv.mdepparse.MayaFileGraph.addFromFiles parse_all_paths still to be implemented