[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: [PATCH] kdesu dialog simplification
From:       Frans Englich <frans.englich () telia ! com>
Date:       2003-12-19 10:59:27
[Download RAW message or body]

On Friday 19 December 2003 08:22, Aaron J. Seigo wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Friday 19 December 2003 12:07, Frans Englich wrote:
> > Hi all,
> >
> >   Patch below removes the line in the kdesu dialog which tells what
> > command it was feeded, ie. "Command: /usr/local/kde_stable/bin/kcmshell
> > clock --lang en_US".
> >
> > Reasons why it's bad to have that line:
> > * It is not informative.
> > * It is repulsive and puts the user in a fraightened mood - just like
> > ERROR codes tends to do.
> > * It makes a simple interface complex.
> >
> > Reasons to have it:
> > * Those with *@kde.org knows what it means.
> >
> > IMHO ofcourse :)
> >
> > What do you think?
>
> perhaps a "Details >>" button that shows/hides the command would be better.
> that way people can see it if they want or need to (think: helpdesk)
> without it being intrusively there all the time.

No, I've changed my mind. It is not an acceptable compromise. 

If a user contacts a helpdesk it will be quite possible to figure out what the 
user is doing anyway, even if the user can't tell the exact command it means 
to invoke the date applet or whatever. Because, the user can just tell that 
she/he invoked the clock applet. The helpdesk already knows what commands are 
invoked or can easily find out, in either case the problem can be 
communicated in other fully sufficently ways.
If, a request from a helpdesk or similar emerges(if you're not talking out of 
experience..) I suggest we re-add it or do the "Details >>" solution, it is 
easy to reverse/implement.

But until such an helpdesk situation becomes real and not is a hypotehical 
situation(if it is..) I suggest we for once try to do something that's not 
overdesigned and instead provide a simple, but yet fully functional UI.

Please tell if there's other reasons beside the helpdesk example to add a 
"Details >>" button.


			Frans

_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]