In some of the new tabs the column order is suboptimal.
We want to start from the order in the certificate list and adapt it to the needs of the new tables:
Name, E-Mail, Status, Valid From, Valid Until, [Protocol], Key ID, [Fingerprint], [Certification Trust], [Origin], [Last Update], [Issuer], [Serial Number], [Tags], [Algorithm], [Keygrip]
Suggestions for tabs, [] means hidden by default:
* User-IDs
* now: EMail, Name, Trust Level, [Tags], [Origin])
* new: Name, E-Mail, Trust Level, [Origin], [Tags]
* Note: mind the spelling of E-Mail, we do want the same spelling everywhere
* Subkeys
* now: [Key ID], Fingerprint, Valid From, Valid Until, Status, Algorithm, Usage, Storage, [Keygrip]
* new: [Key ID], Fingerprint, Status, Valid From, Valid Until, Usage, Algorithm, Storage, [Keygrip]
* Note: Status here is not the same as Status in the main certificate list, here it is: good, expired, revoked, [...]. No "certified" and "not certified"
* Certifications
* now: User ID / Certification Key ID, Name, E-Mail, Valid From, Valid Until, Status, Exportable, Tags, Trust Signature For)
* new: User ID / Certification Key ID, Name, E-Mail, Status, Exportable, Valid From, Valid Until, [Tags], Trust Signature For
* Note: Status here is not the same as Status in the main certificate list, here it is: valid, revoked, [...]
* Smartcard (usually we use "smart card" in texts but for the tabs one word looks better and we write it as one word on the button for the view, too)
* now: [Keygrip], Fingerprint, Token, Type, Serial Number, Owner
* new: [Keygrip], Fingerprint, Owner, Type, Serial Number, Token
* Note: Owner and Type is only available when the card is inserted, otherwise I would tend to hide "Token". And Both columns are not wide, so I'd prefer to have them further on the left then the long ones
For reference: Smart card view table as implemented recently by Ingo for PIV: Card Key (aka Slot), User ID, Fingerprint, Created, Usage, Algorithm, Keygrip, Actions