Path: utzoo!attcan!uunet!cs.utexas.edu!yale!bunker!hcap!hnews!115!778.1!Eric.Bohlman
From: Eric.Bohlman@p1.f778.n115.z1.fidonet.org (Eric Bohlman)
Newsgroups: misc.handicap
Subject: Re: Synthesizer interfacing
Message-ID: <14294@bunker.UUCP>
Date: 20 Sep 90 15:58:36 GMT
Sender: wtm@bunker.UUCP
Reply-To: Eric.Bohlman@p1.f778.n115.z1.fidonet.org
Distribution: misc
Organization: FidoNet node 1:115/778.1 - COPH-2 (BGMS), Chicago IL
Lines: 29
Approved: wtm@bunker.UUCP

Index Number: 10511

[This is from the Blink Talk Conference]

 JP> Are there PD reader-type programs out there?  Is there a 'standard' of 
 JP> good and bad things that I should know, when setting up a configuration 
 JP> specifically to work with these readers, or should I start trying to 
 JP> figure out how to write a self-reading program?

With the possible exception of Enable Reader which is quite old, there aren't  
really any PD readers out there, but most of the commercial programs have demo  
versions available (generally they have a per-session time limit).  Many of  
the demos can be found on BlinkLink or other BBSs that carry this echo.   
Downloading them and reading the manuals (most of the demos have complete  
manuals) would be a good way to get familiar with the facilities that reader  
programs provide.

It would be better to write programs to work with screen readers than to try  
to make them self-talking.  Everyone, blind or sighted, has their own style of  
reading a program's user interface; trying to make a program self-talking  
limits them to your idea of how they should read it, and makes the program  
hardware-dependent.  Getting familiar with the facilities provided with  
readers will help you understand how to structure programs so they can be used  
easily.
 

--
Uucp: ..!{decvax,oliveb}!bunker!hcap!hnews!115!778.1!Eric.Bohlman
Internet: Eric.Bohlman@p1.f778.n115.z1.fidonet.org