[bugs.kde.org] [Bug 360400] Very confusing list of products in search

[Christophe Giboudeaux]

https://bugs.kde.org/show_bug.cgi?id=360400

Christophe Giboudeaux  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Christophe Giboudeaux  ---


*** This bug has been marked as a duplicate of bug 340420 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 360400] Very confusing list of products in search

[Filipus Klutiero]

https://bugs.kde.org/show_bug.cgi?id=360400

Filipus Klutiero  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=340420
 CC||chea...@gmail.com

--- Comment #2 from Filipus Klutiero  ---
I very much agree with this. With the power JavaScript and the web platform has
reached, there should really be a text field to dynamically filter through
products, or - even better - the select multiple should be replaced with a
fancy drop-down like those allowed by the Chosen jQuery plugin.

This will probably be more complicated since components need to be considered
too. Ideally, there would be a single text field where I'd type for example
"korgac". If korgac is defined as a product, then that product would come up as
the first suggestion. If korgac is instead defined as a component of the
korganizer product, then that component would come up as the first suggestion.
I think it would make sense, before attacking this issue, to reconsider the
structure of products and components. Many products are small and have a single
"general" component. Other products are big and have so many components that
some are related; for example, amarok has components "Playback", "Playback/CUE
sheet support", "Playback/Replay Gain", "Playback/Streams". Therefore, for a
small product like abakus, a single-level categorization system would be
better, while for a big product like amarok, a three-level categorization
system would be better. So I think it would be best to allow a variable depth.
A product could have sub-products, and any sub-product may have
sub-sub-products. With this approach, we could put all products/components in a
single widget which would ease filtering.

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 360400] Very confusing list of products in search

[hvm via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360400

--- Comment #1 from hvm  ---
(In reply to hvm from comment #0)
> When filing for a bug, the list of products is pretty confusing. I have a
> hard time finding the name of a product when I know it let alone when I'm
> not sure which is it. 
> 
> The about pages of the applications are not always helpful with this either. 
> 
> It would help a lot if there would be more information in the dropdown -
> official name of the app/product, not just the internal name, version kde it
> was present in (kde4/kde5, plasma whatever, etc) and searching through all
> of these.
> 
> Thanks!
> Voicu

Meant to say, when searching for a bug, i.e. on https://bugs.kde.org/query.cgi

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 360400] Very confusing list of products in search

[hvm via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360400

hvm  changed:

   What|Removed |Added

Summary|Very confusing list of  |Very confusing list of
   |products|products in search

-- 
You are receiving this mail because:
You are watching all bug changes.