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

Move actions from modules to tray #1044

Merged
merged 11 commits into from
Dec 13, 2024

Conversation

iLLiCiTiT
Copy link
Member

@iLLiCiTiT iLLiCiTiT commented Dec 10, 2024

Changelog Description

Moved Launcher, Loader and Console directly to tray actions and removed ayon_core.modules. Also added Publish report viewer action to Admin section.

Additional info

Tools should work as before. Changed label of Loader to Browser, we've discussed it multiple times and if I remember correctly we came to conclusion that it should be Browser. Added Pubish report viewer action which was requested multiple times.

Because the actions are not defined by "addons" their order is not exactly the same.

Testing notes:

  1. All the actions should work as before.

Resolves #858

@iLLiCiTiT iLLiCiTiT added the type: enhancement Improvement of existing functionality or minor addition label Dec 10, 2024
@iLLiCiTiT iLLiCiTiT self-assigned this Dec 10, 2024
@ynbot ynbot added the size/XL label Dec 10, 2024
@MilaKudr
Copy link

One thing to discuss is the order of the tools, many users remember that the launcher was first from the top, now it is second...

@LiborBatek
Copy link
Member

LiborBatek commented Dec 11, 2024

@iLLiCiTiT is there a way to keep Launcher on very top of the menu? I know seems not important but it really is...to maintain the muscle memory.

@m-u-r-p-h-y thougts?

here is the original order:

image

and the new one:

image

P.S.: I love the fact Loader became Browser, perfect!

@iLLiCiTiT
Copy link
Member Author

@iLLiCiTiT is there a way to keep Launcher on very top of the menu? I know seems not important but it really is...to maintain the muscle memory.

I can't keep it in previous order, I can move it under addons actions of above addons actions, both can be confusing. If it is under addons actions then Publisher is at different place. If it is above then e.g. ftrack would be at different place.

@m-u-r-p-h-y
Copy link
Member

m-u-r-p-h-y commented Dec 11, 2024

I can't keep it in previous order, I can move it under addons actions of above addons actions, both can be confusing. If it is under addons actions then Publisher is at different place. If it is above then e.g. ftrack would be at different place.

do not understand the reasoning, but if not possible, then we can do nothing.

I would also rather keep the same order from the previous one as @LiborBatek suggests

and thanks for the Browser !

@m-u-r-p-h-y
Copy link
Member

also @MustafaJafar should be aware of the changes as it will affect the documentation . . .

@iLLiCiTiT
Copy link
Member Author

iLLiCiTiT commented Dec 11, 2024

do not understand the reasoning, but if not possible, then we can do nothing.

Publisher and ftrack (and potentially other) actions are added by addons (dynamically). Launcher and Browser are now defined by tray, which happens at completelly different place not knowing about other actions. I would have to hardcode dependncy on other actions (addons) by label, which is possible, but not very systematic.

Note: The order of addon actions was defined by title of the addon, so changing Loader to Browser would mean that Browser would be always at the top... So I can't use "previous" logic to sort it by title without changing order of Browser action.

Long story short, making this better means that we have to make something a little bit worse.

@BigRoy
Copy link
Collaborator

BigRoy commented Dec 11, 2024

do not understand the reasoning, but if not possible, then we can do nothing.

Publisher and ftrack (and potentially other) actions are added by addons (dynamically). Launcher and Browser are now defined by tray, which happens at completelly different place not knowing about other actions. I would have to hardcode dependncy on other actions (addons) by label, which is possible, but not very systematic.

Note: The order of addon actions was defined by title of the addon, so changing Loader to Browser would mean that Browser would be always at the top... So I can't use "previous" logic to sort it by title without changing order of Browser action.

Long story short, making this better means that we have to make something a little bit worse.

Could we mark the menu entries with custom data like order that could be used to sort by. So the sorting becomes by:

# psuedocode
def sort(action):
    if action.order is not None:
        return action.order
    # sort by label
    action.text

I do think the Publisher is not so high priority over the Launcher that it should be at the top - and hence I feel the change is very confusing and we should look into ways to do set a preferred order.

@iLLiCiTiT
Copy link
Member Author

iLLiCiTiT commented Dec 12, 2024

Could we mark the menu entries with custom data like order that could be used to sort by. So the sorting becomes by:

That would require some api for actions, which we don't have.

I do think the Publisher is not so high priority over the Launcher that it should be at the top - and hence I feel the change is very confusing and we should look into ways to do set a preferred order.

And should be launcher always at the top? Meaning that ftrack would move under it? (Can be achieved even now.)

@BigRoy
Copy link
Collaborator

BigRoy commented Dec 12, 2024

And should be launcher always at the top? Meaning that ftrack would move under it? (Can be achieved even now.)

I personally would say so. But definitely go based off of the opinion of others here please.

@LiborBatek
Copy link
Member

Launcher as the very top/first in the menu? Yes, please!

@iLLiCiTiT
Copy link
Member Author

And Browser at the bottom is ok?

@LiborBatek
Copy link
Member

And Browser at the bottom is ok?

yes, I dont mind being it at the very bottom for Browser at all if the Launcher been on top

@iLLiCiTiT iLLiCiTiT merged commit 2ee0112 into develop Dec 13, 2024
1 check passed
@iLLiCiTiT iLLiCiTiT deleted the enhancement/858-move-tray-actions-to-tray-tool branch December 13, 2024 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/XL type: enhancement Improvement of existing functionality or minor addition
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move Tray actions to tray tool
7 participants