Re: Usability suggestions about the new authorization API for KDE

On Wednesday 15 July 2009 12:29:05 Nicola Gigante wrote:

> I have some idea. The first, for a KPushButton, is to add an icon
> (something like a lock or a key) to represent that the push button
> wil trigger an authentication. This would be useful for actions
> like Save on a kcm module.
> But another pattern is possible. As in (for example) preference
> panes in Mac OS X, an unauthorized user would find all the controls
> in the window disabled until it unlocks a toggle button (which will
> have as the icon a close or open lock). Unlocking will trigger the
> authentication which, if successful, will enable the controls in
> the window.

I don't see the difference, because I don't known what happens in 
first case -- I can only guess that user is allowed to make the 
modifications, but at the save point he/she needs to authenticate.

Is this correct? If yes it is difference:
a) authenticate to save
b) authenticate to edit

Right?

(b) is much more useful.

Cheers,
_______________________________________________
kde-usability mailing list
kde-usability@xxxxxxx
https://mail.kde.org/mailman/listinfo/kde-usability