GNOME Bugzilla – Bug 621951
Should use at-spi2 instead at-spi
Last modified: 2013-01-25 17:44:32 UTC
Dasher should depend on the new a11y framework at-spi2-core and at-spi2-atk instead at-spi More info here: http://live.gnome.org/Accessibility/GNOME3 http://live.gnome.org/Accessibility/BonoboDeprecation
Is it planned to work on this? It is required for GNOME3 which will be soon.
Yes, I thought I would start with http://git.gnome.org/browse/at-spi2-core/commit/?id=ccbc1b958968d210f26b471abb751995f70143f5 (Note that dasher only uses bonobo for speech, and that at-spi2 has no cspi equivalent - so, we are well aware of what is going on, but the bug sounds more straight forward than it is - and more major than it actually is. Talking of speech: speech-dispatcher or OpenTTs anyone?)
Currently OpenTTS, but you could ask in #a11y or on the mailing list?
It seems to have changed back to SpeechDispatcher... Just in case there weren't enough moving targets, glib-dbus -> gio
glib-dbus is not a gnome3.0 requirement.
while i command dasher the following message and warnings are coming and the application starts what is the problem and how to solve this? please help me... ** Message: Opening GUI file: /usr/share/dasher/dasher.traditional.ui ** Message: Opening GUI file: /usr/share/dasher/dasher.preferences.ui ** (dasher:4888): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (dasher:4888): WARNING **: Could not locate registry ** Message: Could not initialise SPI - accessibility options disabled
Patrick, you have lost some accessibility meetings, but FYI. In relation to a C api in order to create an AT you can use libatspi. Current python bindings for at-spi2 are created using gobject introspection on this library. It is not C-SPI compatible, but would allow to create a C AT compatible with at-spi2. So solving this issue for AT-SPI2 would involve moving to a new C API instead of a language migration.
Created attachment 198001 [details] [review] Untested AT-SPI2 patch I took a crack at porting dasher to at-spi2. I'm not sure what's meant by the API not being C-SPI compatible, as it seemed that most things were generally the same. That said, this patch is untested. I haven't gotten it to link, even, though everything seems to be in place.
Could this patch get a review, please?
Any chance I could get some feedback on this patch?
Could you try at least compiling and linking it first? (In the meantime I have written at-spi2-* packages for pkgsrc.org, which have been committed a few weeks ago, so at least I have a libatspi. I am still working on removing all the various editors. After that I will write the equivalent of an external editor using libatspi. A quick look at the patch just looks like replacing old libcspi function names with libatspi...)
Created attachment 213174 [details] [review] Updated patch with linking The email about your comment must have gotten lost in the shuffle. I figured out the linking problem and have modified the patch accordingly. A very, very quick test seems to show it's mostly working, as far as I can tell.
I have finally removed enough spaghetti to add at-spi2 support.
After http://git.gnome.org/browse/dasher/commit/?id=8857b4e8c602b42bb696f1f106f276bd5ea9156a at-spi2 support is function, in addition to Xtst and cspi.