- Please note that if you're developing an application which can rely not just on Qt modules, but also Qt extensions like from the KDE Frameworks, you might want to use instead KAuth from KDE Frameworks.
polkit-qt-1 aims to make it easy for Qt developers to take advantage of polkit API. It is a convenience wrapper around QAction and QAbstractButton that lets you integrate those two components easily with polkit.
polkit-qt-1 is not a direct replacement of polkit-qt: it is based on polkit-1, which is not backwards compatible in any way with Policykit <= 0.9, which was the backend of polkit-qt. You are encouraged to port polkit-qt applications to polkit-qt or KAuth (from KDE Frameworks), since PolicyKit <= 0.9 is no longer maintained.
polkit-qt-1 is split in three libraries: polkit-qt-core-1, polkit-qt-gui-1 and polkit-qt-agent-1
polkit-qt-core-1 lets you control actions and authentication without a GUI, with some very simple functions. It also lets you retrieve and control useful information on the polkit authority. You will be mostly interested in the
polkit-qt-gui-1 lets you easily associate GUI items with polkit actions. Through some simple wrapper classes you are able to associate QAction and QAbstractButton to a polkit action, and get their properties changed accordingly to polkit's result. It includes the classes Action, ActionButton and ActionButtons
polkit-qt-agent-1 lets you write your own polkit authentication agents in a very simple way.
- A sample usage of polkit-qt-1 can be found in Polkit-qt-1 usage example
- Alphabetical Class List
- Class Hierarchy
Documentation copyright © 1996-2023 The KDE developers.
Generated on Tue Jun 6 2023 03:56:20 by doxygen 1.8.17 written by Dimitri van Heesch, © 1997-2006
KDE's Doxygen guidelines are available online.