[g-a-devel]Implementing ATK on Custom Widgets
- From: Marc Mulcahy <marc mulcahy sun com>
- To: gnome-accessibility-devel gnome org
- Subject: [g-a-devel]Implementing ATK on Custom Widgets
- Date: Wed, 23 Jan 2002 04:57:32 -0700
Hi All,
Still attempting to get libzvt accessibility support running. We need to
make a decision as to how and what parts of gail should be exposed. I've
run into an issue with the technique used to provide accessibility for
gtkhtml2-- namely that the accessibility implementation class can't have
any data of its own. This won't work for libzvt, since it *has* to keep
some callback pointers laying around. I could attach a private data
structure to the accessible object using a quark or some such horrid and
ugly thing, but this seems to break the GNOME standard of straightforward code.
I propose that at least we expose GailWidget, so that accessibility
implementations for custom widgets don't have to re-invent the wheel for
the basic functions like name, description, screen geometry etc.
Thoughts?
Marc
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]