Gail next steps (was Re: GTK and ATK)

On 05/10/2011 04:28 PM, Benjamin Otte wrote:
So I've been thinking about accessibility in GTK for a while (since it
broke all the time during the unstable GTK 3 development to be exact).
And I've been wondering how to fix the somewhat sad state of the code
we do have. Unfortunately I have no idea how to solve it, but I have
an opinion about what the problem is.

The TL;DR version is this:
I think the problem is the fact that we support a separate API for

Now for the long version:

Well, some weeks have passed and seems that nobody wants to add anything new to this thread, so I will try to add some conclusions.

First, thanks for this review and proposal. But it is a long term solution, and means so many changes on a lot of different modules, so if it finally implemented, this is a task to be planned for GTK4/glib3. Although this also applies to ATK2.

Summarizing we have on the table two long term proposals:
* Benjamin one about merging ATK and GTK, so the accessibility support towards AT-SPI2 would be more similar to current Qt one (WIP) (although he also implied that the interaction with AT-SPI2 could change)
  * A new ATK2 (some of the tasks related to ATK2 here [1])

In fact, IMHO, some of the issues pointed by Benjamin would be solved by this [2] and the gail migration, but lets not talk about it. As I said, those are long term tasks, and the fact is that the current accessibility status needs to be improved also in the short and medium term.

I also planned to define those short-medium tasks, but after reading again some mails, Matthias already did it in this mail [3], so I will not repeat that. I will just include that as task 1.5 I would include refactoring gailtreeview, one of the big problems related to performance that prevents having a11y enabled as default [5]

Finally, some of us thought that Benjamin was already looking that, starting with the gail-to-gtk, and included that here [4]. It seems that we were wrong to that conclusion. So please, update that section accordingly.


[3] [4]

Alejandro Piñeiro Iglesias (API) (apinheiro igalia com)

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]