I want the extractors to have some options. E.g. as in Pyblish-magenta ExtractAlembic, it has a few options like noNormals, that the user may want to set.
After some research I found these links.
- Pyblish Search and Customisation - where @marcus talks about the option system, but I don’t see this implemented in pyblish.
- Custom UI prototype - the ftrack approach, which is kinda what I want, but they are using a custom UI.
- User Fields in Pyblish QML - which is exactly what I need, but seems unfinished.
So I want to set options for plugins in context and per instance (I want to export normals for Bob, but not for Alice) and I want to use the pyblish-qml as gui. How should I do that?
One thing comes to my mind. Create a preprocess gui before starting pyblish. It would show the options, and set them in the scene (maybe on the export set), then launch the pyblish-qml. But it would mean, my preprocessor gui should run the collectors, and also gather all the VEI plugins to show their options. Then we are just one step away from rewriting the whole pyblish gui, which is not what I want.
Unless you tell me, there is no other way…