| Summary: | Display which backends/sources are represented in the ApplicationDelegate | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Nate Graham <nate> |
| Component: | discover | Assignee: | Aleix Pol <aleixpol> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | adam.golanski, bugseforuns, butirsky, codezela, ianp, notuxius, postix, rdieter, rikmills, thorsten, vasile.dragos, wxl |
| Priority: | HI | Keywords: | usability |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/plasma/discover/commit/933bc4efd516e05b4d00d797524cebc7d023d1f7 | Version Fixed In: | 5.20 |
| Sentry Crash Report: | |||
|
Description
Nate Graham
2018-10-08 23:20:05 UTC
I would rather not. OK, let's re-purpose this to track displaying the source on the delegate like we discussed the other day. *** Bug 401178 has been marked as a duplicate of this bug. *** *** Bug 401778 has been marked as a duplicate of this bug. *** *** Bug 410803 has been marked as a duplicate of this bug. *** At least in 5.16.5, it seems there is a "Source" field, so it sounds to me like this has been implemented. Were we intending some other change I'm not understanding from this conversation? I will say the multiple entries confuse users that don't understand all the different packaging options. Discover is supposed to be "intuitive and simple" (https://userbase.kde.org/Discover#What_Discover_is), so it's not like grouping all the sources under one entry is at odds with the goals of the project. If all the sources are shown with separate install buttons next to them (and perhaps a "recommended" next to the distro package), that seems to also be consistent with the idea that Discover should "try to guide users through safe choices" (https://userbase.kde.org/Discover#What_Discover_isn.27t). Ideally, when an application is available from multiple sources, Discover groups them all into one entry. It already does this for many apps. However this grouping requires that Discover be able to identify all of the different sources of the same app as in fact the same app. To do this, it matches on the app's AppStream ID. When multiple apps have the same ID, Discover understands that they're the same app, and groups them. Unfortunately, many app sources don't provide quality AppStream data, or override the app's own AppStream ID with a made-up one of their choice. Some apps don't provide quality metadata either. And so on. This bug report is requesting a fallback mode that shows the source on each list item so that confused users can see for themselves where the app comes from even when the grouping functionality didn't work because of any of the above issues. If you mean the source would be shown on each item on the list, rather than solely within the individual metadata when you select an item, that sounds like a great upgrade. Yep, that's the idea. *** Bug 417940 has been marked as a duplicate of this bug. *** *** Bug 402093 has been marked as a duplicate of this bug. *** *** Bug 420660 has been marked as a duplicate of this bug. *** Git commit 933bc4efd516e05b4d00d797524cebc7d023d1f7 by Aleix Pol. Committed on 16/06/2020 at 00:41. Pushed by apol into branch 'master'. Show an indicator when the source of the package isn't the default source M +16 -2 discover/qml/ApplicationDelegate.qml https://invent.kde.org/plasma/discover/commit/933bc4efd516e05b4d00d797524cebc7d023d1f7 *** Bug 408212 has been marked as a duplicate of this bug. *** |