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

List:       kde-usability
Subject:    KControl again...
From:       Henrique Pinto <henrique.pinto () kdemail ! net>
Date:       2004-02-05 3:33:31
Message-ID: 4021B98B.2050603 () kdemail ! net
[Download RAW message or body]

Hi people!

Recently, we had lots and lots of discussion about KControl, and most of 
that discussion was pretty useless. It is clear from Aaron's message 
that yet another reorganization won't work, we need  something near to a 
complete redesign. I don't have any ideas for that, unfortunately. (If 
you have a magical solution for all of KControl's problems, please post it.)

However, taking a look at KControl's bug reports at b.k.o, I found some 
interesting problems with some specific KCMs that might be worth 
solving, even though that alone won't solve all of KControl's problems.

Before starting to comment these bug reports, a question. Some time ago 
at this list, there was a big thread about the Sound System KCM. The 
result of that thread was the new KCM that is shipped with KDE 3.2. A 
big difference between that KCM and other modules is that it is much 
more verbose. Instead of relying only on WhatsThis tips for providing 
help, a brief explanation of the option was included directly in the 
KCM. IMO that was a really good thing, as some of the options seemed 
very cryptic for many many users. What do you think about these more 
verbose KCMs? Is it worth having them? What other KCMs need that kind of 
verbosity?

Now the bug reports...

Bug 56903 <http://bugs.kde.org/show_bug.cgi?id=56903>: confusing system 
bell settings (http://bugs.kde.org/show_bug.cgi?id=56903)

    That bug report shows how difficult it is to configure the system 
bell in KDE. It was reported against KDE 3.1.1, but I believe some of 
the comments still aply to 3.2 (my installation is having some problems 
atm, so I can't try it myself). Having an easier way of  configuring the 
system bell would be nice.

Bug 57814 <http://bugs.kde.org/show_bug.cgi?id=57814>: configuration for 
active desktop borders is hard to find 
(http://bugs.kde.org/show_bug.cgi?id=57814)

    As the title implies, the configuration for active desktop borders 
isn't in a place most people would look for it. Actually, the whole 
"Window Behavior" module seems like a mess, and several users already 
asked me where could they disable focus stealing prevention, as they 
didn't figure out where that option was.

Bug 59490 <http://bugs.kde.org/show_bug.cgi?id=59490>: kcontrol default 
email client configuration too difficult 
(http://bugs.kde.org/show_bug.cgi?id=59490)

    Some things in this report seem to be actually bugs, some other 
aspects indicate areas where usability can be improved.

Bug 66691 <http://bugs.kde.org/show_bug.cgi?id=66691>: keyboard tab 
navigation in kcmwallet has confusing order 
(http://bugs.kde.org/show_bug.cgi?id=66691)

    Acording to the report, this bug was partially fixed, but there is 
still one inconsistency. Solving it would be a good thing.

There may be more bugs, I didn't check that carefully. It would be 
really nice if we could manage to solve these. Some of them are in fact 
very simple to solve, like 66691. Any ideas?

--
    Henrique Pinto
    henrique.pinto@kdemail.net
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]