People often do not read the quick-guides for GnuPG VSD.
It seems they just click on the big button "new keypair" although they only use symmetric encryption. This leads to all kinds of confusion later.
Therefore we need at least links to the quick guides and the video on symmetric encryption on the welcome page. I'd like to add some short text on how to decide what to use, too. Or a link to a page where we explain this.
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRAacb518b62740 Use more useful help in welcome page for VSD | |||
| rKLEOPATRAd0ae5ec70106 Update the doc actions for new filenames | |||
I do not agree that this will help much, but I am all for changing the string "Find more info on Wikipedia" into something like "See the Quickguide for a short introduction".
I suggest to make the following text changes for the VSD versions only:
After the first sentence "Kleopatra is…" Insert "\n\nFor password based encryption see this [link to guide| guide].
s/For most actions you need/For public key encryption you need/
And instead of "You can learn more about this on <a href="%1">Wikipedia</a>."
"You can find step-by-step instructions for public key encryption in this <a href="%1">quick guide</a>.
Doing the changes to the text is easy enough, but I'm not sure whether we have a nice way of doing something only in a VSD version.
@ikloecker do you know something? should it just check whether compliance is active?
There's the VERSION file that is used for customizing the About data for VSD and GnuPG Desktop. It's an ini format file that's read with QSettings.
For the links we could use something like action:name-of-corresponding-docaction because the doc-actions already know the correct path of the PDF guides and can open them. Maybe we could make the text depend on the presence/absence of the corresponding doc-actions. Then we could simply hardcode the alternative texts. Not really nicely extensible, but it fits the doc-actions hack. And it would avoid having a link in the Welcome text that points to a not existing file.