Bug 389146 - Kicker's KRunner result UI scales poorly as more runners are added
Summary: Kicker's KRunner result UI scales poorly as more runners are added
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Menu (Kicker) (show other bugs)
Version: 5.11.95
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2018-01-18 10:09 UTC by Christian (Fuchs)
Modified: 2024-03-06 22:15 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian (Fuchs) 2018-01-18 10:09:12 UTC
Currently there is a checkbox to extend the search to files (baloo) and bookmarks. Personally I don't want bookmarks, but I'd like to have files. 

Would be nice if we could check each, sort of 

- Extend search to 
 [ ] files and folders 
 [ ] bookmarks
 [ ] whatever the future holds

instead. It seems to concatenate a string to config currently, so separate entries should not be too hard from a technical point of view, UX is a different thing.
Comment 1 Alexander Mentyu 2018-01-26 17:18:20 UTC
Same wish but for Kickoff - https://bugs.kde.org/show_bug.cgi?id=382760
Comment 2 Nate Graham 2018-02-23 21:51:27 UTC
Kicker and Kickoff use the same backend; marking this as a duplicate of Bug 382760.

*** This bug has been marked as a duplicate of bug 382760 ***
Comment 3 Eike Hein 2018-02-23 21:57:57 UTC
I don't agree with the duping. It's true they use the same backend and have equal abilities to use or not use runner plugins, but whether or not to do so is much more down to the respective UI. E.g. Kickoff uses a single linear list to show all results, Kicker uses a column for each runner. They scale differently.
Comment 4 Nate Graham 2018-02-23 22:05:27 UTC
OK, un-duping. Let's use this bug to track refining Kicker's UI to better support an arbitrary set of runners so it doesn't become comically wide, and we'll keep Bug 382760 to track enabling/exposing the feature for both of them. Does that sound okay?
Comment 5 Eike Hein 2018-02-23 22:08:38 UTC
We can, I'm not sure we've made those decisions yet though :)