[Kde-accessibility] Re: Documentation about ATK and AT-SPI

[Gunnar Schmi Dt]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Wednesday 25 June 2003 21:52, Bill Haneman wrote:
> Thanks very much for this well constructed overview.  It really looks
> great - in fact with your permission I may wish to link to it (once
> final) from our GNOME site since it is in many ways a more concise
> summary than anything we have there.
>
Sure, no problem with that.

> There are a few minor refinements which I'd suggest.
> [...]
I've now updated the document. However, there are some questions that I have 
concerning your comments:

> One thing you didn't mention was the interface "AtkObjectIface" which
> is a special interface which allows objects which aren't subtypes of
> AtkObject to still act like them.  This is a sort of advanced detail so
> perhaps it's OK just to put this in a footnote.  It might turn out to be
> a useful feature for KDE however.
>
I did not find any documentation about AtkObjectIface. However, I do not know 
if we need this interface as it should be possible to create AtkObjects 
within the bridge.

> In addition to the 'register/deregisterApplication' methods, the
> 'notifyEvent' method is of interest to applications since either they or
> their "bridges" must call "Registry.notifyEvent" in order to send
> event notifications to interested clients.  Similarly the applications
> are responsible for sending certain kinds of "key events" to the
> registry when the application receives keystrokes - this is a method of
> AtkUtil which is of interest to non-gtk+ applications and toolkits.
> [...]
I did not find any documentation about the Registry.notifyEvent method or 
similar methods within AtkUtil. From what I've read in the on-line 
documentation I understood that the clients (or the broker) install 
event-listeners, so such a method would not needed.

Gunnar Schmi Dt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE++tcAsxZ93p+gHn4RAppiAKCo9oWWpnoTFUu494/Ybj2rtLpgXwCgrZ4l
rvCMbxUAOlY+PY3cw84SF/E=
=IEcm
-----END PGP SIGNATURE-----