Sure. The plan was to maybe make a new class type to inherit from, but maybe thats not necessary.
True, but the problem is that you need to append instances to the parent instance. This allows the UI to not know about the entire hierarchy before showing. Having to load the entire library of a project can easily become a lot to compute, and to wait for.
Maybe I can have a look at a separate model, but it would need to be build dynamicly anyways.
Again the idea was to not have to load the entire context to begin with, so it was necessary to call the process method every time the user expands an instance.
Defo:) All good things to come. As for the button to import, I'd imagined that you attach actions to the instances, similar to how Pyblish works with its plugins. You would then right-click on an instance to gain access to available actions, where one of them could be to import.
I'm imagining that people would use this GUI for updating the existing scene as well, so one plugin for the GUI would be collecting references in the Maya scene that the user can choose to update.
I've also imagined that you can get more information about the instances, like for example when collecting the references in the Maya scene, you could see that an instance is out-of-date and there are newer versions available.