Re: [g-a-devel] status of cspi?
- From: Ariel Rios <ariel gnu org>
- To: Mike Gorse <mgorse mgorse dhs org>
- Cc: gnome-accessibility-devel gnome org
- Subject: Re: [g-a-devel] status of cspi?
- Date: Mon, 16 Feb 2009 14:57:10 -0600
Cspi was marked for deprecation and python bindings are preferred. I
think your option b is the way to go.
I can elaborate more on this if you want me to.
ariel
2009/2/16 Mike Gorse <mgorse mgorse dhs org>:
> Hi all,
>
> As part of the Mono accessibility work that we are doing at Novell, we need
> to implement the UIA client api and bridge from at-spi. This means that an
> AT written in UIA should have access to applications exposing information
> through atk. As I see it, we have two options for using at-spi in C# /
> .net:
>
> (a) Use cspi, possibly writing a wrapper in C#, or
> (b) write a native C# binding for the dbus-based at-spi.
>
> Can someone here explain the situation with cspi? I am under the impression
> that its usage is sort of discouraged, but I am unsure as to why. Also, can
> someone explain the reasons for replacing python at-spi with pyatspi? (I
> believe the former was similar to option A, but its use is deprecated.) I'm
> just trying to investigate / gather information before we make a decision on
> how to proceed.
>
> Thanks,
> -Mike G-
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]