[nfbcs] Using eclipse with JAWS

Sun Jan 25 05:18:54 UTC 2015

Unless you want one keystroke to get to the package explorer, setting a
different key binding is not necessary; press alt + shift + q then p.
Autocomplete works okay with JAWS. The only problem that I have with it is
that I sometimes have to activate it, cancel it, and then activate again to
get any suggestions to show up. If you get the hang of it, the autocomplete
and autoselection stuff can be really helpful. 

-----Original Message-----
From: nfbcs [mailto:nfbcs-bounces at nfbnet.org] On Behalf Of William
Grussenmeyer via nfbcs
Sent: Saturday, January 24, 2015 7:54 PM
To: Steve Jacobson; NFB in Computer Science Mailing List
Subject: Re: [nfbcs] Using eclipse with JAWS

I always turn the punctuation off when reading code.  It is faster that way,
and any punctuation mistakes are caught with the compiler in the problems
pane.  This has been effective for me.  As for reading capitals, I never
turn it on because the names of variables are always not capital on the
first word and captilized on every sub word.  I assume everyone abides by
this convention.  It only causes problems a few minor times such as when you
have a word like  varSubclass .. then is the Sub capitalized or both sub and
class, etc.  Sometimes people do things differently there.  Last tip is that
you can setup shortcut keys user defined yourself.  I think its under window
-> preferences
-> key bindings.  I setup key bindings to move quickly to the package
manager and the compiler error pane.  I forgot if JAWS works with eclipse
auto complete --  I think it does not but that could have changed.  You can
change settings to turn all auto complete and highlighting off which makes
Eclipse run much faster and Jaws wont lag anymore.

On 1/24/15, Steve Jacobson via nfbcs <nfbcs at nfbnet.org> wrote:
> Nicole,
>
> Thanks, it would make sense that there would be something like that.  
> That kind of feature is an example of something I have found useful, 
> but sighted
>
> people who can have two windows open and visually track see little 
> advantage in using.
>
> Graham, another challenge is to look for different ways of doing the 
> same things, and that can even involve using lesser-known features of 
> an application.  I know I have always been the expert where I work on 
> how to use "FIND" and "SEARCH" commands and sometimes even macros in 
> various environments because they benefit me more than my co-workers.  
> That has even gotten me into some more nitch programming in the past.
>
> Best regards,
>
> Steve Jacobson
>
> On Sat, 24 Jan 2015 19:07:31 -0800, Nicole Torcolini via nfbcs wrote:
>
>>Yes. I think that you just press enter when in the error list.
>
>>Sent from my iPhone
>
>>On Jan 24, 2015, at 3:18 PM, Steve Jacobson via nfbcs 
>><nfbcs at nfbnet.org>
>> wrote:
>
>>Nicole,
>
>>Is there an option in Eclipse to move from an error message to the 
>>line in  the source that caused the error?  I've seen this in other 
>>development
> environments but have not used Eclipse.  If there is such an option,
>>that would probably be helpful to him.
>
>>Best regards,
>
>>Steve Jacobson
>
>>> On Sat, 24 Jan 2015 10:25:50 -0800, Nicole Torcolini via nfbcs wrote:
>>>
>>> Hi. Some of this will get easier as you get used to using JAWS. So, 
>>> in addition to using JAWS for coding, I would recommend using JAWS 
>>> for as much other stuff as possible so that you get used to it.
>
>>> 1. I do not reduce the speed of JAWS to read code. However, please 
>>> note that I have been using JAWS for more than fifteen years, so I 
>>> am used to it.
>>> Also, if you have not already, I would recommend learning Braille 
>>> and asking your employer for a Braille display. This is considered a 
>>> reasonable accommodation because, in most cases, it is unreasonable 
>>> to expect someone to get all of the details verbally that sighted 
>>> people get visually.
>>> Also
>>> note that, in JAWS, you can set different settings for different 
>>> applications.
>
>>> 2. In the voice options, there is an option for capitalization pitch 
>>> change.
>>> In the options for all programs and for each program, there are 
>>> options for when capitals are announced. Again, having a Braille 
>>> display will help with this.
>
>>> 3. In Eclipse, press alt + shift + q to get the list of errors. 
>>> Select the error that you want and press F10 for a list of options, 
>>> including quick fix and details.
>
>>> Finally, I would recommend reading the JAWS help topics on 
>>> keystrokes and settings as you will find a lot of helpful 
>>> information there.
>
>>> Nicole
>
>>> -----Original Message-----
>>> From: nfbcs [mailto:nfbcs-bounces at nfbnet.org] On Behalf Of Graham 
>>> Mehl via nfbcs
>>> Sent: Saturday, January 24, 2015 5:56 AM
>>> To: nfbcs at nfbnet.org
>>> Cc: kmanos1963 at verizon.net
>>> Subject: [nfbcs] Using eclipse with JAWS
>
>>> Hi all,
>
>>> As you may recall from past posts I have made to this list I have 
>>> had some difficulties at work. I am still struggling in a number of 
>>> areas, but I am inching along in progress. With many inovative 
>>> ideaas and some  minimal helpI have developed some crude work 
>>> arounds. Since my last post the update on my limited vision is now 
>>> gone. Doctors are trying to recover the vision but basically my eye 
>>> is dying. So all the skills the NFB and you all have taught me are 
>>> getting thrown into high gear. But I am straying. Now that I have 
>>> some kind of working environment I can develop software. I am 
>>> working on a remote desktop running windows 7 and JAWS 15. I am 
>>> developing using java 8 within eclipse. I probably do not know all 
>>> the hot keys I need to, to help me navigate around quickly, but I am 
>>> learning. There are a couple things that are slowing me down that I 
>>> hope some of you can provide suggestions for me to improve on.
>
>>> 1. I am still not use to high rates of speech on JAWS, which is a 
>>> definite plus. However as many of you may know programming languages 
>>> are not in english terms. So do you all use a high rate of speech to 
>>> read code or do you reduce it to read code?
>
>>> 2. Java standards particularly regarding variable names are written 
>>> in camel case. - meaning take two english words and merge them into 
>>> one word to make a variable name. however the first letter of the 
>>> second word is acapitalized. Is there a setting in JAWS that I am 
>>> missing that will tell me capital letters? I work with other  
>>> software engineers so if I work in their code, I need to know the 
>>> spelling and capitalization because otherwise the code will not 
>>> compile.
>
>>> 3. Fixing errors - from my experience most developers do not write 
>>> clean code the firs time. Once I identify a line of code that has an 
>>> error in it and navigate to the spot the error starts How can I 
>>> quickly identify the
>>> error and fix it.   Let me explain. For those with some vision, if an
>>> error
>>> occurs a visual underline appears under the word or group of words 
>>> forming the error. And if you mouse over it a tool tip appears 
>>> providing details of the error. For those blind I can best describe 
>>> this as in Microsoft word or outlook if a word is misspelled the 
>>> JAWS software speaks "misspelled"
>>> and
>>> the word. In Eclipse instead of speaking "misspelled" it says "invalid"
>>> This
>>> is not very helpful. Is there any way for me to select the "invalid"
>>> string
>>> and get a message like the tool tip to be spoken?
>
>>> Thanks for any help you can provide.
>
>
>
>>> _______________________________________________
>>> nfbcs mailing list
>>> nfbcs at nfbnet.org
>>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>>> To unsubscribe, change your list options or get your account info 
>>> for
>>> nfbcs:
>>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/ntorcolini%40wave
>>> cable.co
>>> m
>
>
>>> _______________________________________________
>>> nfbcs mailing list
>>> nfbcs at nfbnet.org
>>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>>> To unsubscribe, change your list options or get your account info 
>>> for
>>> nfbcs:
>>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/steve.jacobson%40
>>> visi.com
>
>
>
>
>
>>_______________________________________________
>>nfbcs mailing list
>>nfbcs at nfbnet.org
>>http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>>To unsubscribe, change your list options or get your account info for
>> nfbcs:
>>http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/ntorcolini%40waveca
>>ble.com
>
>>_______________________________________________
>>nfbcs mailing list
>>nfbcs at nfbnet.org
>>http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>>To unsubscribe, change your list options or get your account info for
>> nfbcs:
>>http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/steve.jacobson%40vi
>>si.com
>
>
>
>
>
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/wdg31415%40gmail.co
> m
>

--
Bill

_______________________________________________
nfbcs mailing list
nfbcs at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for nfbcs:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/ntorcolini%40wavecable.co
m