RE: Sonified Debugger vs. Screenreader Question
- From: "Lloyd Rasmussen" <lras@xxxxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Wed, 21 Nov 2007 22:59:22 -0500
I use Window-Eyes rather than JAWS, and am not at the level where I am
trying to use an IDE's debugger. But I would strongly recommend you get the
scripts for VS 2005 and JAWS, which were written by blind people on this
list in order to solve JAWS problems and make their work somewhat more
productive. JAWS without the aid of these scripts is probably not even
close to its full potential. People who need to use VS 2005 with JAWS most
likely end up here and install the scripts. That would be one argument for
sticking with VS 2005 rather than immediately jumping on the VS 2008
bandwagon.
Lloyd Rasmussen, Kensington, Maryland
Home: http://lras.home.sprynet.com
Work: http://www.loc.gov/nls
> -----Original Message-----
> From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-
> bounce@xxxxxxxxxxxxx] On Behalf Of Andreas Stefik
> Sent: Wednesday, November 21, 2007 6:46 PM
> To: programmingblind@xxxxxxxxxxxxx
> Subject: Sonified Debugger vs. Screenreader Question
>
> Hi folks,
>
> My research lab is in the process of setting up some experiments
> comparing my sonified debugger (Technically it's a sonified omniscient
> debugger), with the debugger in Visual Studio using Jaws 8.0. I've
> developed a speech based interface that "I hope" will make it easier
> to program for the blind community. I know I've said this before, but
> my tool is a research prototype, not something you can download, but
> nonetheless I hope it will lead folks in the right direction. Anyway,
> my lab and I want this test to be as fair as possible, so I was hoping
> to ask a few questions of the community about how we should have
> everything setup.
>
>
> Basically what we are doing is:
>
> Download Jaws and Visual Studio.NET 2005, and copy the way it allows
> you to navigate and the sounds Jaws outputs into our custom program.
> Then, after our usability testing is complete, we compare the way
> we've come up with experimentally to the current "State of the art" in
> screenreader technology.
>
> Here are my questions:
>
> 1. In Visual Studio, the only way I can find to navigate from the
> editor window, where I type source code, to the watch window, where
> variables are displayed, is by holding CTRL + TAB and using the arrows
> to navigate to that window. For anyone that uses the Visual Studio
> debugger, is this how they navigate, or is another technique more
> common?
>
> 2. If I am in the editor window, where I am modifying source code, and
> I want to determine the "value" of a variable in the debugger, is
> there any way to do that using Visual Studio and Jaws without
> navigating to the watch window? How do folks usually determine the
> current value of a variable in a debugger?
>
> 3. I've heard some about Jaws scripting, but I'm not completely
> familiar with what folks use it for in the context of programming. How
> does Jaws scripting play into this and would or should its use have an
> effect on our experiment in some way?
>
> 4. When we do our final analysis of the navigation, sounds, etc, that
> Jaws and Visual studio uses, we want the setup for our environment to
> be as close to realistic as possible. Are there any settings in either
> Visual Studio or Jaws that we should be adjusting before doing our
> analysis?
>
> Thanks for any help you can provide!
>
> Andreas
>
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
