Committed. Thanks.

In D30134#684292, @yurchor wrote:

In D30134#684291, @okellogg wrote:

I'm not sure whose turn it is, will you commit? Shall I?

Please do if you have access.

In D30134#684291, @okellogg wrote:

I'm not sure whose turn it is, will you commit? Shall I?

I'm not sure whose turn it is, will you commit? Shall I?

Thanks

Laurent kindly took over this, extended and updated this as part of https://invent.kde.org/system/khelpcenter/-/merge_requests/25 (see https://invent.kde.org/system/khelpcenter/-/merge_requests/25/diffs?commit_id=f6d308672a9f68c20585f5d05b6c6032355f850a ) and it was merged in the kf6 branch. This review can be closed.

Just committed this with Albert's suggested change in https://invent.kde.org/graphics/kruler/commit/6cde990b68438aea2dc13199b846fdc37457b52a.

@meven Would you be interested in taking this over? :)

Adding this in the KCM is blocked by the QML port which is blocked by some frameworks stuff. https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1102 is a draft for adding a runner which provides help information. Feel free to try it out & comment on my suggestions.

Todos from last Akademy BoF:

I created the first page at: https://userbase.kde.org/Troubleshooting/Black_Screen

Some ideas from a Kreddit thread
booting to a black screen
mounting drives unsucsessful
fixing dependency errors
Getting sound to work and dealing with IRQ conflicts.
Drivers
connect my smartphone via USB errors
installing applications (.deb especially), Ubuntu PPAs

I would, or just rework https://userbase.kde.org/Troubleshooting and make it show up at https://kde.org/support/ or https://wiki.kde.org/.

Would it make sense to put this into the wiki so it were easy to contribute to? It would need monitoring, obviously, but I think it would encourage others to submit their own problems + solutions. Maybe it would need a template so others could get it right and it doesn't become too chaotic

In D23866#557830, @svuorela wrote:

In D23866#553108, @mlaurent wrote:

Ping ? What is the status ?:)

I'll be happy if someone else takes over. I'm still a bit hung up on other stuff. Don't expect much from me on this before christmas.
/Sune

In D22594#498890, @ngraham wrote:

As for the feature itself, for the past few years I'd been opposed to this, on the basis that people should just use the built-in Baloo-based search instead. But unfortunately the requests keep coming in, and there are use cases that Baloo doesn't work for (e.g. on external disks), so there does seem to be a need, or at least a desire. And we do already have this accessible from the search panel, so this is basically just a shortcut to that. I'll give this patch a fair shake.

And maybe it makes sense to detach these syntaxes from the internal usage (currently only used single runner mode).

That is a good example, thanks a lot!

Okay, thanks. I think I understand all the properties now.

Does this mean we can have any input in a query? i.e. could the "Date and Time" runner have a query with the command "time japan" and then a "Try it" button next to it that copies it to KRunner so the the actual current time in Japan would pop up right there?

But I am not sure this would work because you said they have some internal usage.

The example queries are used in the single runner mode. We don't have to worry about that at all, because we only read all the values.

https://invent.kde.org/network/konqueror/commit/cd6364a2c8a5362c49145204de4eebeff1e4185c

Ah, I forgot I had to land your patches manually.
I'll do it now (already resolving a few conflicts...)

Trying to roll back the diff made to this revision instead of having created a new revision.

• Add ability to drag entries from the sidebar tree

We updated to 3.34 and removed the LiquidThreads extension and are now using the echo extension.

In T13073#238828, @ngraham wrote:

While you're massively overhauling the KCM's user interface, it would be a good opportunity to port the whole thing to QML, too. ;)

While you're massively overhauling the KCM's user interface, it would be a good opportunity to port the whole thing to QML, too. ;)

Just a little addition: If the documentation property exists we could use it instead of the description. This way we wouldn't have to worry about making sure they are in perfectly match with the other one. And then the descriptions still have a purpose, because inline help is still a TODO(while not the priority and there are other issues that have to be sorted out first).

In T13073#238696, @felixernst wrote:

In any case I brainstormed a bit about what would be the ideal solution and this is the best idea I had so far:

Just a little addition: If the documentation property exists we could use it instead of the description. This way we wouldn't have to worry about making sure they are in perfectly match with the other one. And then the descriptions still have a purpose, because inline help is still a TODO(while not the priority and there are other issues that have to be sorted out first).

Sounds good 👍

In T13073#238756, @felixernst wrote:

If I understand you correctly the text would/could then have the following structure:

Runner Name
runner description

[repeat for each syntax] {
   syntax documentation (new optional documentation property - can contain rich text)
   icon
   example queries
   syntax description
   launch button
}

Yeah! It is important to note that the launch button launches the example queries and we can have multiple of them. And regarding the information that is contained in each syntax you are absolutely right. (But I guess you didn't wanted to express the layout here). Also the icon would also be a new property (just to clarify).

Danke für die Blumen :]

Considering that you are implementing KRunner store functionality, would it be feasible for Plugins to ship their own .qml file to provide a (possibly interactive) article?

But there is a help page that is actually useful: https://userbase.kde.org/Plasma/Krunner

That one is completely outdated, unfortunately :/

First of all thanks a lot, those are some awesome ideas!

Firstly: I think this is quite an important thing to solve. IMO most users would be interested in knowing at least the general purpose features of KRunner (like calculation, unit conversion, time zones, window switching) but will only learn about them if they are observant enough and find them by chance.