Can one Simplify the Context Menu?

Asked by Sven R. Kunze

My overall impression on the Context Menu: looks bloated. I would blame the immense amount of separator lines and confusing order. The latter might be a personal preference.

My current context menu:

----------------------
Open in
----------------------
Cut
Copy
----------------------
Move to Trash
----------------------
Rename
----------------------
Bookmark
----------------------
Properties
----------------------
xOOOOOOO
----------------------
Compress
----------------------

My suggestion:

----------------------
Open in
Compress
----------------------
Cut
Copy
Rename
Move to Trash
----------------------
Bookmark
xOOOOOOO
----------------------
Properties
----------------------

Description:
- at least two elements in each group,
- 4 separators less
- 3 groups less
- first group -> what you can do to the content
- second -> what you can do with the path/location
- third group -> bookmarking/managing/marking/highlighting
- last group -> properties

Question information

Language:
English Edit question
Status:
Answered
For:
Files Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Jeremy Wootten (jeremywootten) said :
#1

The number of separators has been question by the design team so it will be looked at, at some point. The main reason for them is that they represent different menu sections that may or may not be present depending on the situation. The alternative would be to grey out items within the same section if necessary.

Your suggested order would not work because it mixes up items added by plugins and contractors (e.g. compress, colour tags) with built-in items and this would cause difficulties.

Revision history for this message
Sven R. Kunze (srkunze) said :
#2

I understand the issue so far.

Wouldn't it help, to create pre-defined menu sections like the ones suggested above?

So, third-party plugins and contractors would need to tell into which menu section they want to add their entries.

Revision history for this message
Jeremy Wootten (jeremywootten) said :
#3

Yes, it could be done, but there would have to be a fair amount of pressure to warrant changing the plug-in/contractor interface.

Revision history for this message
Sven R. Kunze (srkunze) said :
#4

I am just a user here. :)

So, if you find this suggestion helpful, go ahead and use it when the design team feels about looking at the issue again.

Is there anything I can do in the meantime?

Revision history for this message
Launchpad Janitor (janitor) said :
#5

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Sven R. Kunze (srkunze) said :
#6

How do we proceed here?

Revision history for this message
Jeremy Wootten (jeremywootten) said :
#7

You could create a blueprint outlining your proposals at https://blueprints.launchpad.net/pantheon-files/+addspec

Revision history for this message
Sven R. Kunze (srkunze) said :
#8

Can you help with this problem?

Provide an answer of your own, or ask Sven R. Kunze for more information if necessary.

To post a message you must log in.