Re: Proposal: DBus activation of Accessibility
- From: UndiFineD <undifined gmail com>
- To: Matthias Clasen <matthias clasen gmail com>
- Cc: Frederik Gladhorn <gladhorn kde org>, ubuntu-accessibility lists ubuntu com, accessibility-atspi lists linux-foundation org, gnome-accessibility-list gnome org, debian-accessibility lists debian org, kde-core-devel kde org, kde-accessibility kde org, desktop-devel-list gnome org
- Subject: Re: Proposal: DBus activation of Accessibility
- Date: Wed, 18 May 2011 17:05:23 +0200
Currently in Ubuntu Natty 11.04, Dbus in compiz does not work perfectly.
might be better in Ubuntu Classic.
2011/5/17 Matthias Clasen <matthias clasen gmail com>:
> On Mon, May 16, 2011 at 5:29 PM, Frederik Gladhorn <gladhorn 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.
>
> --
> Ubuntu-accessibility mailing list
> Ubuntu-accessibility lists ubuntu com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
>
--
Met vriendelijke groeten,
Keimpe de Jong
(UndiFineD)
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]