Re: Formal complaint concerning the use of the name System Settings by GNOME

2011-07-23 Thread Matthias Clasen
On Fri, Jul 22, 2011 at 5:53 PM, Jeremy Bicha jbi...@ubuntu.com wrote:
 On 22 July 2011 17:17, Ben Cooksley bcooks...@kde.org wrote:

 To be more specific about the problem, installing kde-workspace to a
 GNOME installation results in 2 indistinguishable apps named System
 Settings and 2 named System Monitor. On Ubuntu at least, if I want the
 GNOME version, I have to remember to click the first System Monitor
 but the second System Setting which is awfully frustrating. Here's a
 screenshot from my Ubuntu install:
 https://launchpadlibrarian.net/75745040/Gnome%20Shell%20screnshot.png

This is what happens when you mix and match bits and pieces from
different operating systems. There is really not much that can be done
about it. Since that is what both KDE and GNOME are trying to do:
build complete, self-contained systems. Arguably, KDE is a little
further along, with their big monolithic modules like kde-workspace
that drag in most of the desktop, while GNOME apps can often still be
installed without much of the desktop.

 I'd like to suggest that the GNOME developers consider changing the
 public name of their app to System Preferences. This matches the Mac
 OS X design and arguably GNOME follows some parts of OS X design.
 Furthermore, it is more in line with Gnome 2's SystemPreferences and
 SystemAdministration.

That is an absurd proposal. What next, rename gnome-terminal to
'Commandline Window' because Xfce also ships a 'Terminal' ?!
Generic names don't come with exclusive ownership...

And as has already been pointed out, offering the user a meaningless
choice between 'System Settings' and 'System Preferences' is no less
of a failure than having 2 identical items.


Re: Formal complaint concerning the use of the name System Settings by GNOME

2011-07-23 Thread Matthias Clasen
On Sat, Jul 23, 2011 at 4:41 AM, Ben Cooksley bcooks...@kde.org wrote:

 @Matthias: please explain how this doesn't solve the issue.

It certainly solves the immediate symptom of 'two things in the menu
are named the same'.


Re: Proposal: DBus activation of Accessibility

2011-05-17 Thread Matthias Clasen
On Mon, May 16, 2011 at 5:29 PM, Frederik Gladhorn gladh...@kde.org wrote:
 Hi,
 sorry for cross-posting. I would just like to have this looked at by everyone
 so we can simply implement it.

 During the ATK/AT-SPI hackfest it came up a few times that we have no solution
 to enable accessibility (eg Screen Readers) on the fly. The conclusion was 
 that
 using DBus would fit everyones needs and make it easy for third partys to
 adapt.


 Proposal: DBus activation of Accessibility

I'm not sure how things work on the KDE side, but for GTK+ based
applications, this does not really solve the problem. Since GTK+ a11y
implementation lives in a module that needs to be loaded by all
applications before a11y tools talk to it. We can load the module at
runtime, but at that time widgets may already have instantiated no-op
a11y implementations.