Re: Adventures in calling Atspi from JavaScript
- From: Piñeiro <apinheiro igalia com>
- To: gnome-accessibility-list gnome org
- Subject: Re: Adventures in calling Atspi from JavaScript
- Date: Tue, 24 Jul 2012 16:35:16 +0200
Replying just to have this mail on archives. It seems that if you CC the
mailing list, it is not saved at
https://mail.gnome.org/archives/gnome-accessibility-list
On 07/18/2012 06:03 PM, Joseph Scheuhammer wrote:
> Hi API,
>
> Thanks for your input.
>
>> Askingh all this but in a different way, is all this stuff working fine
>> on C and python but failing on Javascript?
>
> Yes, that may be the crux of the problem. And, maybe I should abandon
> doing this in JS/GObjectIntrospection, and write the tracker in C.
> That is, do all the registering/deregistering/AT-SPI specific stuff in
> a GObject, and provide a .gir interface to that object. Then gs-mag
> (or whomever) would integrate with that. I did something similar (a
> long time ago) with XFixes so the magnifier could access information
> about the mouse.
>
>> I
>> think that your work started with a python prototype written by
>> Joanmarie. Were that prototype using 1) 2) and 3)?
>
> Yes, that's what I based the JS code on, and 1) 2) and 3) all worked
> in Joanie's python prototype. But, I haven't run the prototype in a
> while. I'll check it again to make sure, although I expect it still
> works.
>
> If it matters: A difference is that the prototype uses registry.py
> (part of pyatspi, I think), and doesn't call AT-SPI directly.
> JavaScript can't make use of that registry.py interface.
>
--
Alejandro Piñeiro Iglesias
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]