Re: The top three big problems

  • From: "Andreas Stefik" <stefika@xxxxxxxxx>
  • To: programmingblind@xxxxxxxxxxxxx
  • Date: Sat, 13 Oct 2007 14:10:54 -0700

Do you folks have any ideas as to what would make it easier to
remember all the keystrokes? This type of stuff would be really easy
to add in to my compiler, so suggestions are very welcome!

Andy

On 10/13/07, Andy B <a_borka@xxxxxxxxxxxxx> wrote:
> Good memory I guess... I am in VS2005 almost 50% of the day so have some
> experience with it. Did I remember something wrong?
>
>
>
> -----Original Message-----
> From: programmingblind-bounce@xxxxxxxxxxxxx
> [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Dale Leavens
> Sent: Saturday, October 13, 2007 4:27 PM
> To: programmingblind@xxxxxxxxxxxxx
> Subject: Re: The top three big problems
>
>
> I want to know how you can possibly remember all those key strokes and the
> sequence.
>
>
> Dale Leavens, Cochrane Ontario Canada
> DLeavens@xxxxxxx
> Skype DaleLeavens
> Come and meet Aurora, Nakita and Nanook at our polar bear habitat.
>
>
> ----- Original Message -----
> From: "Andy B" <a_borka@xxxxxxxxxxxxx>
> To: <programmingblind@xxxxxxxxxxxxx>
> Sent: Saturday, October 13, 2007 2:04 PM
> Subject: RE: The top three big problems
>
>
> The below is easily possible in vs2005 at least. If you go into the
> settings, under bu8ild options somewhere (I forgot exactly since I haven't
> been there in a long time), there is a choice to allow the compiler to show
> the error list/window upon build/compile failure. When you are in this list,
> hitting enter on a error message actually instantly jumps you to the code
> line where the error is and highlights it in a certain color. I know the
> color doesn't help a total blind person, but at least jaws jumps to the
> exact line being complained about. All you have to do now is hide the error
> window (alt shift h), fix the line of code and then press f5/control f5/f6
> to rebuild again...
>
>
>
>
> 2. The usability.
>
> A programming environment should be made  thinking to the blind programmers
> needs also, and a blind programmer should be able to configure the
> environment as he wants.
>
> For example, what does a sighted programmer after he runs a program in
> Eclipse or VS.net and it gives an error?
> I think that he looks too se what was the error.
> So, for the sighted programmer is easy to take a look in the wanted pane,
> but a blind programmer should be able to configure the application so after
> it runs the program and gives the error, the focus to be automaticly placed
> in the errors pane. And he should be able to move the focus to the code pane
>
> immediately.
>
> __________
> 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
>
>
__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

Other related posts: