Agreed! JFW is too unstable for me. I have both Screen Readers. Also, JFW is far more flakewise to setup. JFW is too picky about video adapters. I have never seen any of JFW's source code but I bet they've never checked thoroughly for memory leaks and the like. But still, when one application won't work with one Screen Reader, I go to the other and sometimes that's the only solution. Typically, whenever I use JFW, I use it to drive the Braille Display and do't bother with Eloquence which grates on me like somebody scratching a chalkboard and it does a horrible interface to Accent/SA or the Artic Transport which WinEyes does a fairly decent job of. Let's see now! I betya ole David P is gonna get me for this one hahahaha! Amanda -----Original Message----- From: Gregory Nowak <gnowak1@xxxxxxx> To: speakup at braille.uwo.ca <speakup at braille.uwo.ca> Date: Monday, December 24, 2001 1:12 PM Subject: Re: ssh for windows >I don't mean to start a windows screenreader war here, but when I use windows (which is not often), I use window-eyes as I consider jfw to be an inferrior product just like most jfw users feel about wineyes. >Greg > > >On Mon, Dec 24, 2001 at 12:28:29PM -0500, Barry Pollock wrote: >> if your program talks at all with jaws. >> just write a script. >> the jaws script language is quite simple. >> just take a script file from a similar program, >> modify its source and save it to the name of the executable you are using. >> compile it and away you go. >> there are lots of examples in the jfw scripts directory. >> Barry >> >> >> >> _______________________________________________ >> Speakup mailing list >> Speakup at braille.uwo.ca >> http://speech.braille.uwo.ca/mailman/listinfo/speakup > >_______________________________________________ >Speakup mailing list >Speakup at braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup >
