On 22/11/14 20:29, Magdalen Berns
wrote:
Just pointing which of those methods deprecated methods in order to answer your question below.
Deprecated.
Deprecated.
Deprecated.
Deprecated.
Deprecated.
After looking a
little, after your mention on last weekly meeting, I discovered
that this Atk interface is not supported by at-spi2 (so not
supported by pyatspi2 either). It will be likely deprecated.
Deprecated.
Initially, I will not focus on the deprecated methods. It is true that those could be important if someone is using an old version of pyatpsi2/orca, but if that scenario, it will be really likely to be using an old version of java-atk-wrapper too.
I didn't know that there were problems with the focus. If that is also a problem, then it is true that it would be also a good first task.
Some context from the past (so the situation when java-atk-wrapper was maintained by Sun/Oracle). at-spi defined some window related windows, and expected applications to send those signals. For some reason, there isn't any ATK interface defining those signals. But as I said, they were expected in any case. So what in the end each implementors (like gtk) were defining and sending those events on a specific format, and the atk bridge forwarding them, because it knew the format. Really error-prone and without any documentation at all. After a quick look on java-atk-wrapper, that was also done there, defining those events on jawobject.c Since Atk 2.2, there is an interface AtkWindow, that only define those signals: https://developer.gnome.org/atk/unstable/AtkWindow.html#AtkWindow.signals So, my advice is removing those signals from jawobject.c, and implement/wrap AtkWindow where it makes sense. If you want an example, this is how it was done on clutter: https://git.gnome.org/browse/clutter/commit/?id=a9690a4a5e8604652048f32e2ea188aa40e0ae95 It was more removing that adding, so I hope it would be similar on jaw.
Done. BR -- Alejandro Piñeiro (apinheiro igalia com) |