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 less used actions from main context menu in submenus #2518

Open
teamcons opened this issue Dec 5, 2024 · 1 comment
Open

Move less used actions from main context menu in submenus #2518

teamcons opened this issue Dec 5, 2024 · 1 comment
Labels
Needs Design Waiting for input from the UX team

Comments

@teamcons
Copy link

teamcons commented Dec 5, 2024

Problem

Less used actions, such as "Send in mail", create noise when looking for common actions such as "Move to trash" or "rename"

Proposal

Identify a list of actions that could be moved into a "More actions" submenu, below of "Open with"

i may edit this FR once i have access to our eOS puter, but off of the top of my head:
-Send by email
-Create shortcut

This would make the file manager more focused, and in the same breath provide room for extending it

Prior Art (Optional)

Nemo, in Cinnamon, has a "More tools" where user can expand with community-made "Actions"
Nemo and Nautilus have a scripts folder, allowing users to create custom actions on files via shell scripts

@teamcons teamcons changed the title Order less used actions from main context menu in submenus Move less used actions from main context menu in submenus Dec 5, 2024
@jeremypw
Copy link
Collaborator

jeremypw commented Dec 5, 2024

I agree the context menu for file items has become rather long. I think most items provided by contractors and plugins could be moved into a subfolder. These include "Send by Email", "Send by Bluetooth", "Compress", "Apply color tag", "Set as Desktop background/Wallpaper". Incidentally I noticed there now seems to be two items that do the same thing (set the background) so that needs sorting out. I'll raise a separate issue for that.

Flagging for design team input before implementing.

@jeremypw jeremypw added the Needs Design Waiting for input from the UX team label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Design Waiting for input from the UX team
Projects
None yet
Development

No branches or pull requests

2 participants