Publisher: Promote information to be shown on instance label

[bradenjennings]

Changelog Description

We need to be able to display more information on instance label in publisher than just it's name.

In this case for example renderCompositingMain could show there also frame range or some badge that review will be created.

What information shown there could be decided by plugins themselves. But how to solve conflicting interests, available ways to show things, etc. is up to the implementation.

Please see this ticket for more info: https://app.clickup.com/t/6658547/AY-2474

Additional info

Paragraphs of text giving context of additional technical information or code examples.

Testing notes:

1. start with this step
2. follow this step

[bradenjennings]

I wasn't sure how to approach this ticket.

So for now I've added an extra label attribute which can be implemented in the creator plugin.
The problem is I can't return anything useful from the creator plugin method get_extra_label, such as frame range.

I'm hardcoding the frame range for now, for the purpose of demonstration.

Any guidance would be appreciated.

[iLLiCiTiT]

It should not be done via a method on a create plugin, it does not make much sense, you want to show the information per instance and get the information from instance. But there already is a way how to approach it, just fill "label" key in data. That is not enough?

[BigRoy]

It should not be done via a method on a create plugin, it does not make much sense, you want to show the information per instance and get the information from instnace. But there already is a way how to approach it, just fill "label" key in data. That is not enough?

I believe the original new publisher designs had a special layout for the cards to e.g. show the frame range below the instance's name, and potentially make room for other info:

• frame ranges
• asset + task names
• enabled output types
• etc.

Anyway, what's suitable info for there I guess isn't really defined. Maybe @mkolar has a good link to some of those designs (and can debate whether they are still relevant or not).

Just wanted to remark that even if frame range would be in the label - it'd still need to update when e.g. frame range attributes would be "changed" on e.g. creator attributes or publish attributes if those frame ranges are defined there - and not collect or whatever? (Again coming back to the "update on attribute changes"?)