[Bug 199326] System Settings should write default application changes for non-KDE apps

Duncan 1i5t5.duncan at cox.net
Tue Dec 1 01:13:30 GMT 2009


https://bugs.kde.org/show_bug.cgi?id=199326


Duncan <1i5t5.duncan at cox.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |1i5t5.duncan at cox.net




--- Comment #4 from Duncan <1i5t5 duncan cox net>  2009-12-01 02:13:28 ---
Indeed.  Taking a hint from the way the Prince thing was handled, I've taken to
referring to it something like this:

"'The application formerly known as kcontrol' (generically aka 'system
settings', even tho system settings is not only way to generic to be
descriptive, but it controls not system settings, but kde settings, so 
kcontrol is way more accurate in any case, when I can use it to configure my
boot services, /then/ it might arguably be 'system settings', until then, it's
kcontrol, or 'the application formerly known as kcontrol')."

Of course, I'm forced to do something similar with "The application formerly
known as ksysguard" as well, since there's all sorts of "system monitor"
plasmoids, etc, non of which are actually "the application formerly known as
ksysguard" plasmoids, as it doesn't appear to have one...  These generic names
are useless for what names are /for/, actually identifying something.  That's a
problem.  If I wanted functionality descriptions, there's a menu option for
that.  There's a reason I don't have that checked.  I want application names,
and I want them to usefully identify the application, not be so generic as to
be almost useless.

So consider this a request to either change the name back, or to support every
distribution and platform that kde runs on system settings (including Gentoo,
what I run), thus making the name accurate, even if that still won't solve the
generic aspect.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list