You know, I think the scripting engine of Window-Eyes is going to be just fine. I'm sure one can just switch to his/her language of choice and still be fine, since Window-Eyes is COM-based, which makes it pissible to program in any language that supports COM automation.
On 9/12/14, Jeff Weiss <jwe...@wsblind.org> wrote: > That's good to know. > I'm not a professional programmer, and I like VbScript very much. > Jeff Weiss > > > > > -----Original Message----- > From: Aaron Smith [mailto:asm...@aisquared.com] > Sent: Friday, September 12, 2014 9:35 AM > To: gw-scripting@gwmicro.com > Subject: RE: VBScript Alternatives > > Before this gets too carried away, understand that Microsoft removed > VBScript support in Internet Explorer only. They did not remove scripting > support, nor do they have plans to remove scripting support, from the > operating system itself. Again, Microsoft is not abandoning VBScript; it's > use is too ubiquitous, even by Microsoft itself. Just recently we were > provided with some internal Office testing tools from the Office team. Guess > what language those tools were written in? > > To reiterate what's already been stated, the draw of Window-Eyes 'scripting' > is that you can use whatever language you want. We've written apps in > VBScript, Jscript, Python, C# and C++. Each has their own advantages and > drawbacks, just like every other language. In the end, use what matters most > to you. > > Thanks, > > Aaron > > -- > Aaron Smith > Web Development * App Development * Product Support Specialist Ai Squared * > 725 Airport North Office Park, Fort Wayne, IN 46825 > 260-489-3671 * www.aisquared.com > > To insure that you receive proper support, please include all past > correspondence (where applicable), and any relevant information pertinent to > your situation when submitting a problem report to the Ai SquaredTechnical > Support Team. > >> -----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 >> > > > -- Jesus Kevin Morales
