On 06/27/2011 05:18 PM, Matthias Clasen wrote:
Another week gone by, time for another status update on the a11y branch of GTK+.
- We have more tests in tests/a11y:
* a tree-performance test that compares populating a large treeview
with / without accessibles
* a text test that checks
Another week gone by, time for another status update on the a11y branch of GTK+.
- We have more tests in tests/a11y:
* a tree-performance test that compares populating a large treeview
with / without accessibles
* a text test that checks most of the AtkText interface for labels,
entries and
On 06/20/2011 06:18 AM, Matthias Clasen wrote:
I think we should probably give a quick status update.
Thanks for the update. Just a question.
In the last week, Benjamin and I have started to implement the outlined plan.
Achievements so far:
- Code has been moved from modules/other/gail to
No, there is no such plan in the short term. I was just trying to clarify
how things will fit together.
On Jun 20, 2011 8:59 AM, Piñeiro apinhe...@igalia.com wrote:
On 06/20/2011 06:18 AM, Matthias Clasen wrote:
I think we should probably give a quick status update.
Thanks for the update. Just
Piñeiro apinheiro at igalia.com writes:
On 06/07/2011 05:06 PM, Emmanuele Bassi wrote:
5) figure out new interfaces for GTK to expose necessary features to
a11y (and other consumers, such as IM and OSK)
we should probably establish some common interfaces so that Clutter can
expose
On Mon, Jun 6, 2011 at 11:17 AM, Piñeiro apinhe...@igalia.com wrote:
I don't think we can treat that as a first step and hold off on doing
any other fixes until that migration is done. The migration is a
significant undertaking, and will not be finished for 3.2.
Sorry, I didn't want to say
On 2011-06-07 at 09:46, Matthias Clasen wrote:
I don't think we can treat that as a first step and hold off on doing
any other fixes until that migration is done. The migration is a
significant undertaking, and will not be finished for 3.2.
Sorry, I didn't want to say that we should
On 06/07/2011 03:46 PM, Matthias Clasen wrote:
So, I've discussed the best way forward for this with Benjamin today.
Here is a rough 6-step plan for dealing with the 'gail problem':
0) write tests for accessible implementations
1) move modules/other/gail nach gtk/a11y
2) add tons of private
On Tue, Jun 7, 2011 at 11:06 AM, Emmanuele Bassi eba...@gmail.com wrote:
0) write tests for accessible implementations
1) move modules/other/gail nach gtk/a11y
2) add tons of private headers for private structs, to share things
3) remove now unnecessary code
4) add a11y features support to
On 06/07/2011 05:06 PM, Emmanuele Bassi wrote:
5) figure out new interfaces for GTK to expose necessary features to
a11y (and other consumers, such as IM and OSK)
we should probably establish some common interfaces so that Clutter can
expose the same functionality for its own items — and so
On Tue, Jun 7, 2011 at 11:08 AM, Piñeiro apinhe...@igalia.com wrote:
4) Is also an awesome plan (proper shared libgailutil replacement).
A very quick-and-dirty sketch of this can be found in the drop-gail branch:
On 06/07/2011 05:11 PM, Matthias Clasen wrote:
On Tue, Jun 7, 2011 at 11:06 AM, Emmanuele Bassieba...@gmail.com wrote:
0) write tests for accessible implementations
1) move modules/other/gail nach gtk/a11y
2) add tons of private headers for private structs, to share things
3) remove now
On 2011-06-07 at 17:16, Piñeiro wrote:
On 06/07/2011 05:11 PM, Matthias Clasen wrote:
On Tue, Jun 7, 2011 at 11:06 AM, Emmanuele Bassieba...@gmail.com wrote:
0) write tests for accessible implementations
1) move modules/other/gail nach gtk/a11y
2) add tons of private headers for private
On 2011-06-07 at 17:13, Piñeiro wrote:
On 06/07/2011 05:06 PM, Emmanuele Bassi wrote:
5) figure out new interfaces for GTK to expose necessary features to
a11y (and other consumers, such as IM and OSK)
we should probably establish some common interfaces so that Clutter can
expose the same
On Sat, Jun 4, 2011 at 8:44 PM, Piñeiro apinhe...@igalia.com wrote:
About this specific case it is about improve the documention:
http://developer.gnome.org/atk/stable/AtkObject.html#AtkObject--accessible-name
Or something else?
Well, more than that, really.
We need to know for each
On 06/06/2011 04:33 PM, Matthias Clasen wrote:
On Sat, Jun 4, 2011 at 8:44 PM, Piñeiroapinhe...@igalia.com wrote:
About this specific case it is about improve the documention:
http://developer.gnome.org/atk/stable/AtkObject.html#AtkObject--accessible-name
Or something else?
Well, more than
On 06/03/2011 06:01 PM, Matthias Clasen wrote:
On Wed, Jun 1, 2011 at 7:48 PM, Piñeiroapinhe...@igalia.com wrote:
On 05/10/2011 04:28 PM, Benjamin Otte wrote:
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.
On Wed, Jun 1, 2011 at 7:48 PM, Piñeiro apinhe...@igalia.com wrote:
On 05/10/2011 04:28 PM, Benjamin Otte wrote:
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
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
19 matches
Mail list logo
