some more reworking of the reference classes and functions.  the reference class now uses a referenceNode as it's basis, because if we store the refNode as a PyNode, we can quickly and automatically get any updates made to its name.  almost any reference info can be queried using the refNode (withou resorting to a path, which might change without us knowing), including resolved and unresolved paths.  namespaces are still the one weak spot, for which we must first get a path with copy number.  the use of a refNode precludes the need for the caching system, so long as using referenceQuery to get file paths when they are needed provides adequate performance. in general, because almost all the internal queries use the refNode, there should be little need for the paths, except for displaying to the user.
some more reworking of the reference classes and functions.  the reference class now uses a referenceNode as it's basis, because if we store the refNode as a PyNode, we can quickly and automatically get any updates made to its name.  almost any reference info can be queried using the refNode (withou resorting to a path, which might change without us knowing), including resolved and unresolved paths.  namespaces are still the one weak spot, for which we must first get a path with copy number.  the use of a refNode precludes the need for the caching system, so long as using referenceQuery to get file paths when they are needed provides adequate performance. in general, because almost all the internal queries use the refNode, there should be little need for the paths, except for displaying to the user.


git-svn-id: ebd26f0b4afd3fb7c0e0d88f39b62381954d19ac@1129 64d93f2f-123f-0410-81d3-998474c5a783

AtonLerin/pymel,cgrebeld/pymel,leonsooi/pymel,shrtcww/pymel,assumptionsoup/pymel,david-lassonde-adsk/pymel,assumptionsoup/pymel,david-lassonde-adsk/pymel,AtonLerin/pymel,juggernate/pymel,juggernate/pymel,shrtcww/pymel,leonsooi/pymel