https://bugs.kde.org/show_bug.cgi?id=404978
Bug ID: 404978
Summary: Make drawer & action items more composable to support
custom UI patterns
Product: frameworks-kirigami
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: h...@kde.org
Target Milestone: Not decided
In my application, I would like to realize the following architecture:
* Use an AbstractApplicationWindow, as ApplicationWindow packs too much UI and
features I don't use or want/need.
* Use an OverlayDrawer, as ContexDrawer doesn't work with
AbstractApplicationWindow and has UI I don't want or need (e.g. a heading above
the actions) and is also used in a way I don't like (I can have an
OverlayDrawer in a page and therefore lazy-load it, while a ContextDrawer must
be assigned to an (Abstract)ApplicationWindow prop and is therefore global).
* Inside the OverlayDrawer, I'd like to present a combination of custom UI and
a hierarchical action menu much like ContextDrawer can do.
In trying to do this, I face the following challenges:
* The delegate item used by drawers concert with Kirigami.Action is not public
API.
* The listview item used to hold action delegates and its behavior is not
public API.
I'd like to see changes to make all of this more composable and flexible, e.g.:
* Make ContextDrawer more flexible to use, lifting the limitations mentioned
above.
* Make action list views and action delegate items public API, so they're
usable in custom OverlayDrawer host items.
--
You are receiving this mail because:
You are watching all bug changes.
