GPG Keychain: Cleanup of File menu and Key menu
I read the discussion here:
http://support.gpgtools.org/discussions/problems/27796-gpg-keychain...
about adding yet another option to the context menu. I’m not gonna discuss that specific command and if it deserves a place in the context menu but instead I created this thread about some cleanup in the menus:
Too many options in the context menu. I think the context menu should have the most important commands, but not all. For example, is Algorithm Preferences really that important? It’s not even in the menu bar at all. Here’s the context menu:
The logic behind some items’ place in either the Key meny or the File menu. Mail Public Key is in File, but Send public key to Keyserver is in Key. (Also notice different capitalization). Export and Import is in File while Generate is in Key.
Here’s the File menu:
and here’s the Key menu:
In my opinion, the Key menu should be about stuff you do with a certain, existing key. The File menu should contain the most basic commands: Import and Export is correctly placed in File (all of Apple’s application do this), but I think Mail Public Key should join the others in the Key menu.
Generate I think should move from Key to File and perhaps renamed to Generate Key. This is similar to basically all applications where you create something new and I don’t think a GPG key is fundamentally different than let’s say a text document in TextEdit.
Although, I don’t think Search for Key should move to another menu, it fits well into the other Keyserver related commands in Key. So I guess that’s the exception to the rule.
What do you think of this?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Steve on 17 Dec, 2014 10:40 AM
Hey Leveebreaks,
thanks for this input. It's very valid and GPG Keychain could use a general overall cleanup of it's menu structure.
Algorithm Preferences
https://gpgtools.lighthouseapp.com/projects/65684/tickets/311 covers the algorithm prefs which indeed should be moved to the top menu.
Mail Public Key
About "Mail Public Key..." being in File menu: what you write is true.
Move "Mail Public Key..." from top menu file to top menu > Key: https://gpgtools.lighthouseapp.com/projects/65684-gpg-keychain-acce...
and replace "Generate..." with "Create New Key..." under top menu > File: https://gpgtools.lighthouseapp.com/projects/65684-gpg-keychain-acce...
Thanks for bringing this to our attention and the very useful and details report.
Kindly,
steve
Support Staff 2 Posted by Steve on 29 Jan, 2015 11:09 PM
Leveebreaks, all three tickets are fixed. Feel free to verify via the latest nightly GPG Suite: https://releases.gpgtools.org/nightlies/
Kind regards,
steve
Steve closed this discussion on 29 Jan, 2015 11:09 PM.
leveebreaks re-opened this discussion on 07 Feb, 2015 07:39 PM
3 Posted by leveebreaks on 07 Feb, 2015 07:39 PM
Thanks, looks good. Although, my OCD noticed the "Create" in "Create new Key". Usually Mac applications leave this out, and only display "New" or "New [something]". (I didn't think about this when writing the first post in this thread)
Support Staff 4 Posted by Steve on 07 Feb, 2015 07:55 PM
Yes that's right. And if you are in Word or Pages it's pretty obvious what "New" will do. Since new users tend to be overwhelmed with all the crypto info they are flooded with, I'm hesitant, since to many "new" might not mean a lot in a software called GPG Keychain.
What do you think?
Thanks for the Transifex pings. We'll need to address that soon, but need more time.
5 Posted by leveebreaks on 08 Feb, 2015 12:40 PM
I think you're right, an encryption application needs more explanatory commands than a word processor. My complaint was really just about it not being as visually pleasing as the standard "New [something]". So if you keep "Create new key" I will have no problem with it.
Support Staff 6 Posted by Steve on 08 Feb, 2015 12:47 PM
Hm could use "New Key..." instead of "Create new key..." that should be explanatory enough.
Support Staff 7 Posted by Steve on 08 Feb, 2015 01:47 PM
#329 attached to this discussion. Renaming to "New Key..."
Steve closed this discussion on 01 Jun, 2015 01:34 PM.
Support Staff 8 Posted by Steve on 04 Jun, 2015 05:11 PM
All tickets have been closed.
Steve closed this discussion on 04 Jun, 2015 05:11 PM.