Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Promote information to be shown on instance label in Publisher #136

Open
antirotor opened this issue Feb 28, 2024 · 3 comments · May be fixed by #167
Open

Promote information to be shown on instance label in Publisher #136

antirotor opened this issue Feb 28, 2024 · 3 comments · May be fixed by #167
Assignees
Labels
backlog added into backlog type: feature Adding something new and exciting to the product

Comments

@antirotor
Copy link
Member

antirotor commented Feb 28, 2024

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

image

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.

[cuID:AY-2474]

@jakubjezek001 jakubjezek001 added the backlog added into backlog label Feb 28, 2024
@MustafaJafar MustafaJafar added type: feature Adding something new and exciting to the product and removed feature labels Jul 11, 2024
@dee-ynput
Copy link

Related to #167 but not linked (yet?)

@iLLiCiTiT
Copy link
Member

Should the value change based on changes in creator attributes?
Should be the label stored in scene?
Do we have any other use-case in mind?

@BigRoy
Copy link
Collaborator

BigRoy commented Oct 18, 2024

Should the value change based on changes in creator attributes?

Yes, please.

Should be the label stored in scene?

I'm fine with the creator being able to compute/define it dynamically.

Do we have any other use-case in mind?

It may be more than 'label' but just showing metadata like start frame, end frame, colorspace or whatever would be nice to 'promote' and visually show on the instance for easy debugging. However, once we go down that route I feel we may first need some 'redesign' to pinpoint WHAT makes sense in design?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog added into backlog type: feature Adding something new and exciting to the product
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants