kde-accessibility@kde.org
[Top] [All Lists]

Re: [Kde-accessibility] [Accessibility] Re: D-Bus-based accessibility AP

Subject: Re: [Kde-accessibility] [Accessibility] Re: D-Bus-based accessibility API
From: Willie Walker
Date: Tue, 21 Aug 2007 12:20:03 -0400
On Tue, 2007-08-21 at 07:04 +0200, Olaf Schmidt wrote:
> [ Willie Walker, Di., 14. Aug. 2007 ]
> > Given that it sounds like the Trolltech API and the AT-SPI are identical
> > for the intents and purposes of such testing, I'd guess one could pick
> > several pairs of apps (one from GNOME, same sort of one from KDE) and
> > conduct studies such as latency, packet size, CPU usage, memory usage
> > and the user and assistive technology interact with the apps.
> 
> The difficulty, of course, is then that we are dealing with different 
> applications which might have speed differences themselves. So we are not 
> truly testing the speed of the API.

True, but it should hopefully help give us an idea.

> > Yep!  That's why I proposed/pushed for the creation of the pyatspi
> > bindings and why we purposely tried to hide CORBA/ORBit/Bonobo stuff.
> > Knowing the current implementation of pyatspi, I suspect it may become a
> > bit of work at the pyatspi binding level to handle both the CORBA and
> > DBUS solutions.
> 
> Yes, it might indeed be a bit of work, especially if we want to use both of 
> them at the same time.

I think we have a number of users that want to use KDE and GNOME
applications side by side.

Will


_______________________________________________
kde-accessibility mailing list
kde-accessibility@xxxxxxx
https://mail.kde.org/mailman/listinfo/kde-accessibility

<Prev in Thread] Current Thread [Next in Thread>