Revisions and Commits
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | • aheinecke | T5175 Kleopatra: Add support for custom groups | ||
Resolved | • aheinecke | T5239 Add UI for managing groups | ||
Resolved | • aheinecke | T5273 Release Gpg4win 4.x.x |
Event Timeline
Added a first version of the UI. Key list still needs to be changed from a simple list view to the usual multi-column tree view.
Currently, the dialog for editing groups can only be opened from the group details dialog (which can be opened by clicking on the icon shown in the encryption recipient input field).
I think this is now ready for testing.
Open questions:
- The UI lists only groups defined in Kleopatra's configuration. Should groups that are defined in gpg.conf also be listed (as read-only)?
- Should it be possible to make copies of groups? This would be useful for migrating old groups defined in gpg.conf. But it may also cause problems if people make copies of immutable groups that are defined in the global system configuration.
Hi, thanks I'll give it a spin tomorrow.
I don't think so. The groups in gpg.conf so far were more of an expert feature as there was no gui for this and anyone who reads the gpg manpage is in my opinion an expert user. So I don't think we should put any effort in that.
- Should it be possible to make copies of groups? This would be useful for migrating old groups defined in gpg.conf. But it may also cause problems if people make copies of immutable groups that are defined in the global system configuration.
Yes I think that would be nice to have if it is not too much trouble. Even without the migration use case. The use case I am thinking of is more that you have a group "Department X" and you Copy it as "Project Y" and then add some external keys to the Project but you still have your "baseline" department group.