Plans for revamping Kiosk and KAuthorized

[Aaron J. Seigo]

On September 23, 2009, Gary Greene wrote:
> Another thing to note about the kiosk framework is that it also allowed
> administrators to "tailor" the profile as well so you could hide not just
> the various actions, but also the menu, etc. There are a number of things
> that kiosktool does that are far off from the authorization of actions.

right; these are all accomplished using the same mechanisms which fall into 
one of two categories: [KDE Action Restrictions] and [KDE Resource 
Restrictions].

the action restrictions, which includes things like hiding the menu (pls 
correct me if i'm wrong there), are all simple string:bool pairs so any system 
that implements support for KAuthorized::authorize will automagically work for 
KAuthorized:authorizeAction.

this is because authorizeAction() just call authorize() internally :)

so from the perspective of KAuth, this is all the same thing.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090923/fd9cfa2e/attachment.sig>