Re: [Kde-accessibility] Questions regarding AT-SPI and ATK
- From: "Padraig O'Briain" <Padraig Obriain sun com>
- To: gunnar schmi-dt de, peter korn sun com
- Cc: gnome-accessibility-list gnome org, kde-accessibility mail kde org, vohi trolltech com
- Subject: Re: [Kde-accessibility] Questions regarding AT-SPI and ATK
- Date: Wed, 30 Jul 2003 08:24:48 +0100 (BST)
ATK depends only on glib.
I have noticed that AT-SPI has dependencies on gtk+ and gail. I am not sure why
the dependency on gial is there. As for gtk+, it is used in some of the test
programs. It is also used in the directory atk-bridge which builds a GTK module
which is loaded into programs at initialization to provide accessibility
support. If KDE were to use AT-SPI it would need a similar mechanism.
Padraig
> > 5. In order to get an acceptable solution for KDE we have to evaluate the
> > dependencies of those parts of the GNOME Accessibility Architecture that
> > will be used within KDE. When looking at ATK and the broker I fear that
> > both will most likely have too much dependencies. However, as we currently
> > do not have a clear position of KDE to AT-SPI, so I cannot say which
> > dependencies will be OK and which have to be changed.
> >
> > If what I heard is correct the ATK dependencies are due a dependency on
> > GAIL which was introduced in order to force the user to have a working
> > architecture once ATK is installed. This dependency on GAIL pulls a
> > dependency on GNOME into ATK and should be avoided if we decide to use ATK
> > in KDE.
>
> Hmmm... Perhaps Padraig or someone else can speak to this, but I didn't
> think that ATK depends upgon GAIL. The reverse is true.
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]