In addition to running a plug-in once for every instance as in the previous example, it can sometimes be useful to define "classes" of instances that a common set of plug-ins can operate on.
Here, a "class of instances" is known as a family and a plug-in may support one or more families, which is another requirement attribute, like hosts.
1
import pyblish.api
2
3
items =["john.person","door.prop"]
4
5
classCollectInstances(pyblish.api.ContextPlugin):
6
order =0
7
8
defprocess(self, context):
9
for item in items:
10
name, suffix = item.split(".")
11
instance = context.create_instance(name)
12
instance.data["families"]=[suffix]
13
14
classPrintPersons(pyblish.api.InstancePlugin):
15
order =1
16
families =["person"]
17
18
defprocess(self, instance):
19
print("Person is: %s"% instance)
20
21
classPrintProps(pyblish.api.InstancePlugin):
22
order =1
23
families =["prop"]
24
25
defprocess(self, instance):
26
print("The prop is: %s"% instance)
27
28
pyblish.api.register_plugin(CollectInstances)
29
pyblish.api.register_plugin(PrintPersons)
30
pyblish.api.register_plugin(PrintProps)
31
32
import pyblish.util
33
pyblish.util.publish()
34
# The person is "john"
35
# The prop is "door"
Copied!
If you pay special attention to the final output, you can see that "john" was processed by PrintPersons, whereas "door" got processed by PrintProps.