Preparing for the webinar made me think of Pyblish in a new light, and I've discovered a new way of breaking it down to the layman. Let me know what you think of this idea of constraints and types to introduce plug-ins and families.
What is Pyblish?
If PUBLISHING is sharing with constraints, then PYBLISH then is a means through which you define and manage these constraints.
Constraints range from..
- This file must go into this location
- Models cannot have locked normals
- This asset must be registered with our asset tracking software
- to anything anything along those lines.
Each CONSTRAINT is written in the Python programming language and encapsulated in a "plug-in" - a subclass of one out of two superclasses, depending on the kind of behavior you are looking for - global or local.
Plug-ins are typically stored in one file each and discovered at run-time, similar to Python's import mechanism.
Each constraint is associated with a user-defined TYPE, such as a model, rig, animation or composite, such that each type can be managed independently.
CONSTRAINTS are known as plug-ins
TYPES are known as families