Hi.  What did you do to Visual Studio 2013 to make it work?  I am
finding that intellisense does not work, and if I press tab it goes to
some strange place and the end key goes to another file.  I can
certainly read the actual code.  I am using c# rather than vb.net.  What
options did you change to make it work better with screen readers?

Rick Thomas <ofbgm...@mi.rr.com> wrote:

> Hi Bruce:
> Visual Studio or any of the free modules have to be setup for accessibility
> with a screen reader.
> That said it works quite well once setup and the rather large learning curve
> is mastered.
> I use vb.net 2013 for Desktop with few problems with WindowEyes out of the
> box except with the forms designer and the lack of support for reading line
> numbers as in prior versions of Visual Studio related products.
> After reading Aarons reply to this thread I am not sure this discussion is
> worth much except where someone might want to learn another language for
> their own  personal use.
> If he is correct and VBScript might be supported for many years to come
> VBScript offers the general scriptor the best and most intuitive way to do
> some app development.
> Since I havent done much scripting recently I have no dog in this race
> anyway.
> If I create a app that doesn't require the use of the WE Object model I work
> in vb.net for the most part.
> If I end up working on something the WE Model I will consider my options at
> that time.
> Later and, again, congratulations on your project.
> Rick USA
> 
> -----Original Message-----
> From: LBX [mailto:lab...@fltg.net] 
> Sent: Friday, September 12, 2014 10:14 AM
> To: gw-scripting@gwmicro.com
> Subject: Re: VBScript Alternatives
> 
> Hi Rick,
> 
>     Yes, the .net I had taken 2 courses last year on them. The issues are
> the readability of the menu's...
> 
>     The Python is OK but has reading an Issue using a screen reader. Modules
> are version specific, based on what version of the C++ library and Windows
> keeps changing it, so you have to be aware of it.
>     Now the based way to avoid them is keeping a stable version of Python
> but modules are a pain when having to keep track of the version it was
> compiled under.
> 
> 
>     The .net is OK to use, you also have to pay attention to what is focused
> when inserting code and such.
> 
>     but if the WE module were to go to that, maybe we could end up with a
> better reader for the .net menus which could make everyone happy.
> 
>     Chip had done this with the VBA and using the Word ability to list the
> code choices. That would also be the way to go with the .net, having an easy
> list of events and such to insert into the code at the cursor location and
> such.
> 
>     Power Shell allows for the shell commands which is like Python and such,
> but it is a way to go to get access to the Windows Com and such. But shell
> has limitations in terms of display and screen events...
> 
>     If you get into Python, you will find it is an entirely different animal
> and as you noted, indenting is a pain for screen reader programs unless you
> turn on the space count feature, then you will get a lot more talking which
> can end up being annoying. At least it would tell you how many spaces of
> indent you have for Python, besides the arrow key movement when going up or
> down; where blank lines mess up that ability to align things.
> 
>     So I think the .net is the way to go when Windows decides to get rid of
> VbScript. For we as programmers could have easier usage of the C++ to write
> apps with; making the code run much fast with less issues of timing and such
> for events.
> 
>         Bruce
> 
> 
> Sent: Friday, September 12, 2014 9:54 AM
> Subject: RE: VBScript Alternatives
> 
> 
> Hi Bruce: The 2 takeaways I got was that Python UI is not all that
> accessible for screen reader users and that indentation is important which
> is also a pain to track while programming for blind programmers.
> Otherwise I am not a fan of "Open Source" modules since they tend to not
> consider accessibility by most non visually impaired users and once a
> developer creates a module they tend to stop support of the module over time
> as they get involved in other things.
> But, if Python supports com efficiently and the UI can be made very
> accessible to screen reader users I don't see why it may not be a candidate.
> Actually, I lean twoard the .net framework but that may just be my personal
> background in it and based on my lack of deep knowledge of other languages I
> don't know if there would be a better choice.
> If GW goes in the .net direction we could put together some documentation,
> some tutorials and perhaps, like Chip, some classes in learning to script
> using whatever .net language was recommended IE vb.net, c# or C++ etc...
> Rick USA
> 
> 
> 
> ---
> This email is free from viruses and malware because avast! Antivirus
> protection is active.
> http://www.avast.com
> 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         cov...@ccs.covici.com

Reply via email to