Re: Proposal: DBus activation of Accessibility
On Wednesday 18. May 2011 23.21.47 Mackenzie Morgan wrote: > On Wed, May 18, 2011 at 3:38 PM, UndiFineD wrote: > > https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/749084 > > The interface Frederik outline above isn't under the > org.freedeskop.compiz namespace, so I'm not sure this would actually > block starting AT-SPI stuff. CC'ing him for input. Sorry, but I don't understand how this is related. Unless compiz disables dbus completely, this should not matter. Cheers, Frederik -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Proposal: DBus activation of Accessibility
On Wed, May 18, 2011 at 3:38 PM, UndiFineD wrote: > https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/749084 The interface Frederik outline above isn't under the org.freedeskop.compiz namespace, so I'm not sure this would actually block starting AT-SPI stuff. CC'ing him for input. -- Mackenzie Morgan -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Proposal: DBus activation of Accessibility
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/749084 2011/5/18 Mackenzie Morgan : > On Wed, May 18, 2011 at 11:05 AM, UndiFineD wrote: >> Currently in Ubuntu Natty 11.04, Dbus in compiz does not work perfectly. >> might be better in Ubuntu Classic. > > This wouldn't apply til 11.10 or maybe even 12.04. Whatever's wrong > with DBus should get fixed though. Has a bug report been filed? > > -- > Mackenzie Morgan > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > -- Met vriendelijke groeten, Keimpe de Jong (UndiFineD) -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Proposal: DBus activation of Accessibility
On Wed, May 18, 2011 at 11:05 AM, UndiFineD wrote: > Currently in Ubuntu Natty 11.04, Dbus in compiz does not work perfectly. > might be better in Ubuntu Classic. This wouldn't apply til 11.10 or maybe even 12.04. Whatever's wrong with DBus should get fixed though. Has a bug report been filed? -- Mackenzie Morgan -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Proposal: DBus activation of Accessibility
Currently in Ubuntu Natty 11.04, Dbus in compiz does not work perfectly. might be better in Ubuntu Classic. 2011/5/17 Matthias Clasen : > On Mon, May 16, 2011 at 5:29 PM, Frederik Gladhorn 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) -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Proposal: DBus activation of Accessibility
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 Problem description: We need a cross-desktop solution to dynamically activate the accessibility framework. Ideally we could switch on accessibility functionallity by default. At the moment it seems that most solutions use quite a few resources, therefor the best short-term solution would be to find a way to enable accessibility on the fly. As an example this is helpful when on first time use or when the computer is shared with users that have no accessibility needs. Currently Gnome requires the user to log out and back in. KDE has no solution. Proposed solution: To activate accessibility, a dbus notification is sent to inform about the state of the accessibility framework. The enabled status of the accessibility framework can be queried via the same mechanism. A setter is also provided to activate the accessibility framework desktop wide. The DBus interface contains a property that says whether accessibility is enabled, has a notification signal and a method to enable accessibility. Currently the at-spi2 dbus registry would be the best place for this functionallity. DBus service: org.a11y.Bus Proposed DBus interface: Gnome could couple this with the existing gconf notification. For KDE the system settings module will have to be extended. Greetings, Frederik -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Proposal: DBus activation of Accessibility
On Mon, May 16, 2011 at 5:29 PM, Frederik Gladhorn 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
