Re: [Kde-accessibility] Use of gconf key '/desktop/gnome/interface/accessibility' on KDE ?



On 6/26/06, Bill Haneman <Bill Haneman sun com> wrote:
On Mon, 2006-06-26 at 08:19, Ashu Sharma wrote:
> Hi,
>
> There was discussion about making use of ATK on KDE, rather than
> putting in another CORBA implementation to talk to AT-SPI (to avoid
> dependency on GNOME-related libraries). I'm not quite clear as to what
> was finally decided.

If KDE writes to ATK, it makes the job easier in a number of ways (at
the cost of introducing a glib dependency, but hiding other gnome-ish
dependencies).  However, the AT-SPI layer requires CORBA in order to
function, so in order to actually expose useful information to our
assistive technologies, an application must LD_PRELOAD the "atk-bridge"
module which bridges from ATK to AT-SPI's CORBA IPC.

I think this is the most effective thing to do for the time being
(preload atk-bridge), since it doesn't introduce a CORBA dependency on
the KDE apps (only a soft runtime dependency).  The AT-SPI assistive
technology clients cannot work without the AT-SPI/ORBit2/etc. libraries
being present on the system anyhow, so from a practical perspective this
is the minimum current dependency situation.

There's another environment variable you can look for if you don't want
to use gconf; GTK_MODULES.  Of course that's still quite a
gnome/gtk+-ish variable and arguably not appropriate to KDE anyhow, so
it might be cleaner just to spawn a gconf-client executable and parse
the output, in order to detect whether assistive technology support is
desired or not.  Also, soon there will be a slightly different mechanism
for detecting the presence of the AT-SPI registry - it will place an IOR
as an Xatom on the root DISPLAY window.  This means you can find it
without using bonobo-activation.

regards

Bill

>
> On a related note, is the gconf
> key '/desktop/gnome/interface/accessibility' used on KDE too, to set
> or find if accessibility support is to be enabled on a system? Or, is
> it used only on GNOME?
>
> Thanks,
> Ashutosh
>
> ______________________________________________________________________
> _______________________________________________
> kde-accessibility mailing list
> kde-accessibility kde org
> https://mail.kde.org/mailman/listinfo/kde-accessibility



Bill,
Thanks for these details.
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) .
Thanks,
Ashutosh


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