https://bugs.kde.org/show_bug.cgi?id=478174
ratijas <m...@ratijas.tk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #1 from ratijas <m...@ratijas.tk> ---
Hi,
I totally agree with you. Filtered navigation UX can and should be improved.
I'd imagine a complete solution would consist of three parts:
- A model would provide a filtering layer: roles such as whether a row matches
at all, and ranges of sub-matches. KItemModels feels like the right place for
it.
- Then a specialized view would negotiate the filtering state with said model,
presenting current search text and reacting to key press events as appropriate.
- Finally, a specialized delegate would need to render sub-matches as
highlighted regions. FYI there is such implementation in Zeal, the
documentation browser: https://github.com/zealdocs/zeal/pull/1475
In case of QtWidgets, KItemViews seems like a good fit for view and delegate
types; except it is a Tier-1 framework, meaning it can't depend on KItemModels.
That sucks, but I'm sure we'll figure something out. And then we'd also need
something for QML/QtQuick.
--
You are receiving this mail because:
You are watching all bug changes.
