At least in VSD an entry in the Help menu should link to the FAQ on the relaunched gnupg.com website.
And to be discussed:
Should we add further info? I suggest we should create a glossary page on the website and link to that, too.
To mitigate confusion between "key", "certificate" and "password" (or passphrase). (The latter one is also referred to by some people as "key", especially in the context of symmetric encryption.)
| rLIBKLEO Libkleo | |||
| rLIBKLEOddac03561e85 Add url parameter to docaction | |||
| rLIBKLEO869ffed5e780 Add url parameter to docaction | |||
| rLIBKLEOfddcabc0c70c Add url parameter to docaction | |||
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRA70f5a145af4f Adapt to docaction API change | |||
| rKLEOPATRA9890a0cf6564 Adapt to docaction API change | |||
| rKLEOPATRAd6768dd85b88 Adapt to docaction API change | |||
| rKLEOPATRA326e67763057 Adapt to docaction API change | |||
Tobias can you add this please and extend libkleos DocAction so that it handles a web URL as an alternative to a file?. And takes an optional additional paramter for "show" which then depends not on weather or not the file exists but on something like "is_vsd()"
The API should both accept a file an an URL. e.g. for the GnuPG Manual. We ship that ib the matching version in VSD but not in Gpg4win,. So in Gpg4win it could link to https://gnupg.org/documentation/manuals/gnupg/ if the pdf file is not found.
I just want to remind you that we have added the possibility to explicitly disable opening of any URLs in Kleopatra. Don't introduce a new way to open a URL which cannot be disabled via the same setting.
Can you clarify on what the show parameter is intended to do? I don't yet see how it would be useful, as the distinction between VSD and gpg4win is already made by whether the respective file is present or not
For the FAQ link we do not want to ship a file but only use an online link but it should only be shown in VS-D mode. MMh thinking about this some more we also want to sow it in GnuPG Desktop (the not VS version) I am unsure yet how to detect this. Maybe with about data infos?
I think the DocAction idea doesn't really work well because it leads to empty submenus and bogus actions in the toolbar configuration and the keyboard shortcut configuration in builds that don't include the PDFs. And now, it seems, checking whether a file exists isn't enough anymore.
I think we need to rethink the way custom actions are added to the different gpg4win builds. Maybe the help menu actions should be created dynamically on runtime from information in some file that exists only in gpg4win instead of being created hard-coded and unconditionally as DocActions and then just hidden.