On 6/26/06, <b class="gmail_sendername">Bill Haneman</b> <<a href="mailto:Bill.Haneman@sun.com">Bill.Haneman@sun.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, 2006-06-26 at 08:19, Ashu Sharma wrote:<br>> Hi,<br>><br>> There was discussion about making use of ATK on KDE, rather than<br>> putting in another CORBA implementation to talk to AT-SPI (to avoid<br>> dependency on GNOME-related libraries). I'm not quite clear as to what
<br>> was finally decided.<br><br>If KDE writes to ATK, it makes the job easier in a number of ways (at<br>the cost of introducing a glib dependency, but hiding other gnome-ish<br>dependencies). However, the AT-SPI layer requires CORBA in order to
<br>function, so in order to actually expose useful information to our<br>assistive technologies, an application must LD_PRELOAD the "atk-bridge"<br>module which bridges from ATK to AT-SPI's CORBA IPC.<br><br>I think this is the most effective thing to do for the time being
<br>(preload atk-bridge), since it doesn't introduce a CORBA dependency on<br>the KDE apps (only a soft runtime dependency). The AT-SPI assistive<br>technology clients cannot work without the AT-SPI/ORBit2/etc. libraries
<br>being present on the system anyhow, so from a practical perspective this<br>is the minimum current dependency situation.<br><br>There's another environment variable you can look for if you don't want<br>to use gconf; GTK_MODULES. Of course that's still quite a
<br>gnome/gtk+-ish variable and arguably not appropriate to KDE anyhow, so<br>it might be cleaner just to spawn a gconf-client executable and parse<br>the output, in order to detect whether assistive technology support is
<br>desired or not. Also, soon there will be a slightly different mechanism<br>for detecting the presence of the AT-SPI registry - it will place an IOR<br>as an Xatom on the root DISPLAY window. This means you can find it
<br>without using bonobo-activation.<br><br>regards<br><br>Bill<br><br>><br>> On a related note, is the gconf<br>> key '/desktop/gnome/interface/accessibility' used on KDE too, to set<br>> or find if accessibility support is to be enabled on a system? Or, is
<br>> it used only on GNOME?<br>><br>> Thanks,<br>> Ashutosh<br>><br>> ______________________________________________________________________<br>> _______________________________________________<br>> kde-accessibility mailing list
<br>> <a href="mailto:kde-accessibility@kde.org">kde-accessibility@kde.org</a><br>> <a href="https://mail.kde.org/mailman/listinfo/kde-accessibility">https://mail.kde.org/mailman/listinfo/kde-accessibility</a><br><br>
</blockquote></div><br><br>Bill,<br>Thanks for these details. <br>I am actually wondering about the current state of KDE accessibility - whether AT clients under KDE currently depend on gnome/gconf libraries (especially if they use the gconf key '/desktop/gnome/interface/accessibility' to enable AT support)
<span style="font-size: larger;"></span>.<br>Thanks,<br>Ashutosh<br>