RE: WindowEyes Getting Script Language

  • From: "Ken Perry" <whistler@xxxxxxxxxxxxx>
  • To: <programmingblind@xxxxxxxxxxxxx>
  • Date: Sun, 3 Feb 2008 07:08:31 -0800

I have found you get better answers from google if you use words together
with com for example "com interface .net"  or com object interface"  but it
would help if we knew what language your planning on writing in.  Just about
any language ahs a com interface so you pretty much can chose anything.
Tell me what your going to be writing in and I can try to find you some


From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Thomas
Sent: Saturday, February 02, 2008 5:47 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: WindowEyes Getting Script Language

Hi JP:
Any suggested readings on very basics of Comm Programming?
I'm having Google mess mixing Comm up with Communications.  Any Keywords,
W3c Keywords or url's that might help me get started setting up homework?

Also, if you have any tutorial url's could you let me know?
I'm trying to find out how to get started by Googling for now.
Rich; Farmington Mich. USA
From: Macarty, Jay  <mailto:Jay.Macarty@xxxxxxxx> {PBSG} 
To: programmingblind@xxxxxxxxxxxxx 
Sent: Saturday, February 02, 2008 4:06 PM
Subject: RE: WindowEyes Getting Script Language

I agree that this sounds promising. I just finished reading the introduction
to Window-Eyes scripting published by GW. Exposing Window-Eyes objects
through COM and letting the script writer choose the language they are
comfortable with certainly adds some flexibility. Of course it carries the
responsibility of being aware of your audience if you are writing scripts
you wish to share. I could probably write some nice scripts in ruby or
AutoIt (and will probably do so for my own use) but for sharing, I'd want to
make sure the script was written in a language such as VBScript or JScript
which I could expect anyone to have installed. As for your question about
.net managed code, I have written other C# programs which accessed COM
objects and the intro from GW says it will be accessible from .net. 
I think this was a very interesting design approach by GW Micro and will be
anxious to see how it pans out. Throwing out a scripting framework which
lets one use things like VBA, VBScript, JScript, and so on certainly opens
the door for the rapid growth of user written and contributed scripts. 


From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Thomas
Sent: Friday, February 01, 2008 7:18 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: WindowEyes Getting Script Language

Hi Gang:
WindowEyes is getting a Scripting Language, finally!  OK, so they say it
will use Com Automation and various languages can be used with the default
language VB Script.
First, I know some of you are really good with such thingys as Com
Automation having done accessibility work.  Is there some good starting
points on learning to write scripts, or they say we can use compiled
programs like c++, and Com Automation?
What about the Managed Code of
I have always used Windoweyes but it needed some fixes in applications like
Visual Studio and some Internet Controls weren't accessible, oh ya, java
script sometimes gave it fits.
I'm kind of excited.
Rick Farmington Mich. USA

Other related posts: