mix of cmds and openmaya input, for now always provide both as input due to how the original validation function is written.
but would be a good example of problem areas to investigate regarding “converters”
running these tests on a cube is instant in the original tool, but takes about 1 second in pyblish. likely pyblish logging / print overhead
when running time tests on a larger scene, it takes noticable time (10 seconds) in pyblish QML
but near instant in pyblish.util.publish()
so seems to be a pyblish UI thing. both QML and lite
maybe related to the refresh?
since we run 25 validations on 14 meshes (=350 refreshes)
Still ideally it should run at same speed and show where we are.
might have to optimise the GUI
using pip is hard for artists. so a self contained setup would be great.
maya has plugins/modules which can be setup to work independent, and handle their own env variables. this is great for people who dont script etc. since you just drag n drop the module in the modules folder.
examples: