PolicyKit integration in KDE take 1: systemsettings and kcmshell

Sebastian K├╝gler sebas at kde.org
Tue Mar 10 13:53:03 GMT 2009

On Monday 09 March 2009 18:38:30 Dario Freddi wrote:
>  - How to implement this on the GUI side? I thought about two options: 1)
> just make the "Apply" button call PolicyKit if needed 2) Add an "Unlock"
> button that makes all the widgets in the module active (just as GNOME
> does). I personally favor for the first, if we can get some nice icons
> (think about the shield in Vista).

I think we'll need to look at three cases here:

1 no password needed
2 password needed
3 password needed, but cached

For #1, it's probably fine to do it fully transparant. For #2, there should be 
an indicator that a password is needed, so a user that doesn't know the 
password won't bother changing anything just to be told "you're not allowed 

#3 is a bit tricky, since in this case we get there are some consistency 
considerations, i.e. why does it sometimes require a password? It might make 
sense to fold this into 2 still, but then we get "why does it say it needs a 
password, but doesn't ask for it?", and along with it "did it actually work 
without the password (while it indicated it needs authorization)?"

Just some thoughts on those UI bits ... looking forward to your work hitting 
my machine :-)

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 489 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090310/fa3fe1e8/attachment.sig>

More information about the kde-core-devel mailing list