RE: SSIP for Windows -- beta almost ready for release
- From: "Macarty, Jay {PBSG}" <Jay.Macarty@xxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Sun, 2 Dec 2007 19:56:43 -0600
Jamal,
Thanks! I had taken the API code for Jaws pretty much right out of the source
for EdSharp. I looked at the code for accessing Window-Eyes and SAPI but
decided to go with the assembly built from the tlbimp command since it seemed
easier to implement. Had missed the code for SA but will take a look.
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui
Sent: Saturday, December 01, 2007 12:16 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: SSIP for Windows -- beta almost ready for release
Currently, JAWS has an unofficial API (no documentation by Freedom
Scientific. Window-Eyes, HAL, and System Access also have APIs.
Window-Eyes uses a COM server for this, whereas the others use Win
API calls to standard DLLs. the HAL/SuperNova one is the most
extensive, though it controls the synthesizer software, itself, rather
than the screen reader. Unfortunately, I found it not to be usable by a
language other than C++ (which would not be a problem for you) because
it involves hooking into window messages at a low level.
The Window-Eyes and System Access APIs essentially just let one pass a
string of text to be spoken by the current voice of the screen reader.
The JAWS one additionally has support for calling a JAWS function or
script in the currently active set of scripts (usually default.jss and
application-specific.jss).
I recently posted C# code that has wrappers for speaking a string with
JAWS, Window-Eyes, System Access, or SAPI5. Similar code may be found
in the open source EdSharp distribution available at
http://www.EmpowermentZone.com/edsetup.exe
The default location for the main source code file is
C:\Program Files\EdSharp\EdSharp.cs
Cheers,
Jamal
On Fri, 30 Nov 2007,
Dónal Fitzpatrick wrote:
> Date: Fri, 30 Nov 2007 22:30:48 -0000
> From: Dónal Fitzpatrick <dfitzpat@xxxxxxxxxxxxxxxx>
> Reply-To: programmingblind@xxxxxxxxxxxxx
> To: programmingblind@xxxxxxxxxxxxx
> Subject: RE: SSIP for Windows -- beta almost ready for release
>
> Can I intrude a very daft question here... I didn't know there were
> screenreader API's. Could anyone point me in the direction of documentation
> on their use?
>
> My reason for asking is that I'm working on an EU sponsored project at the
> moment which aims to provide blind/visually impaired people access to
> diagrams in a distance-Ed or e-learning environment. There is a debate in
> the consortium about whether to go self-voicing or to tap into the
> screenreader the person is using. I'd be interested to play with both
> options. We're writing, incidentally, in C++ with a front-end in WX.
>
> Thanks for any information.
>
> Dónal
>
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
