[x] I have searched the existing issues and added correct labels.
Please describe the feature you have in mind and explain what the current shortcomings are?
Publish families should match node types, like rop.flipbook for flipbook nodes and rop.opengl for OpenGL nodes. This method lets us target plugins to specific node types.
Here are more examples:
rop.alembic: Different ROP nodes that export Alembic files don't share the same node type name alembic. For instance, the SOP/Alembic ROP is named rop_alembic, while the ROP/Alembic ROP is simply alembic.
rop.geometry: Geometry ROP nodes can export multiple representations, such as BGEO and VDB.
Suggested implementation?
Could we use callbacks for this purpose?
Or should we update the get_publish_families method?
Or should we update collect_instances?
I think updating the get_publish_families method where we pass the created node can be helpful.
we already have access to the creator identifier and product_type via self.
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
Publish families should match node types, like
rop.flipbook
for flipbook nodes androp.opengl
for OpenGL nodes. This method lets us target plugins to specific node types.Here are more examples:
rop.alembic
: Different ROP nodes that export Alembic files don't share the same node type namealembic
. For instance, the SOP/Alembic ROP is namedrop_alembic
, while the ROP/Alembic ROP is simplyalembic
.rop.geometry
: Geometry ROP nodes can export multiple representations, such as BGEO and VDB.Suggested implementation?
Could we use callbacks for this purpose?
Or should we update the
get_publish_families
method? Or should we updatecollect_instances
?I think updating the
get_publish_families
method where we pass the created node can be helpful. we already have access to the creator identifier and product_type viaself
.Additional Info
This topic was mentioned in this comment https://github.com/ynput/ayon-houdini/pull/167#discussion_r1844951027 to reflect the node type in families.
Describe alternatives you've considered:
No response