I think krunner is an underrated tool because for a new user it is extremely difficult to know how it works. Not just to open documents or programs. For example, what command do you have to use to do a google search? Explain it to me like I'm a kid, please.
I did a mockup with an example.
Created attachment 110012 [details] Mockup krunner An example of mockup to show more help
(In reply to francisco_t from comment #0) > I think krunner is an underrated tool because for a new user it is extremely > difficult to know how it works. true! On top of that, if you try to ameliorate this dire situation in the wiki (by editing), you'll meet with a lot of hostility there so you drop that idea real quick.
Well, the help feature existed in the KDE4 version of KRunner and it was very similar to the mockup provided by francisco t. According to the comments on the bug 216368, people were complaining about the bad design of that help feature and the feature has been removed. In the wiki this feature is still documented: https://userbase.kde.org/Plasma/Krunner#Discover_KRunner For me, even if not perfect, the KDE4 help feature was not bad, for sure infinitely better than not having it.
(In reply to Simone Gaiarin from comment #4) > Well, the help feature existed in the KDE4 version of KRunner and it was > very similar to the mockup provided by francisco t. > > According to the comments on the bug 216368, people were complaining about > the bad design of that help feature and the feature has been removed. > > In the wiki this feature is still documented: > https://userbase.kde.org/Plasma/Krunner#Discover_KRunner > > For me, even if not perfect, the KDE4 help feature was not bad, for sure > infinitely better than not having it. My idea is a very *simple* and quick help. If you need more information or to learn in depth, linking to the wiki is the best option. That was my intention with the link "+info".
I agree with you. What I meant is that the code for the feature as you describe it already exists and probably it just needs to be ported to KDE5. The point is that there should be enough support from the users for this feature to come back.
"Just" means rewriting it in QML. I once made a mockup and did a proof of concept but I didn't get VDG feedback on it, so I lost interest.
Ah ok, did not think about the QML port. Could you open a new task on phabricator for this and publish your mockup? (or attach it to this bug). I will give my feedback. I added Nate Graham to the CC of this bug, I am pretty sure he will also help on this. I think this would be a very useful feature, and given that you already did something on this matter it is a pity not to finish it.
> For example, what command do you have to use to do a google search? I agree, this is not at all obvious. Kai, please feel free to continue your work! I'm sorry that you didn't get any feedback from VDG before, but the group is much more active now, as you can see. :) We'll happily look at your work if you can dredge it up again.
The concept of inline help looks very nice! Also we are considering multi-line results which should allow us to document multiple syntaxes (for an inline help approach). *** This bug has been marked as a duplicate of bug 369136 ***