Hi Marlon,
Welcome!
The first thing you should be aware of is that the Window-Eyes scripting
methodology is not a proprietary one as is the case with Jaws. It employs
industry standard COM automation and has the VBScript run-time engine
built-in. It also has Microsoft's JScript engine, but I would recommend the
use of VBScript as there is much more documentation available on it and the
Window-Eyes documentation focuses primarily on it as well. So COM automation
and VBScript is the place to start. Excuse me if this is at all redundant to
the Jaws implementation. I know absolutely nothing about it other than it
being a proprietary one. Therefore, I have no idea of references and
parallels which are common between the two.
Good luck,
Tom
----- Original Message -----
From: "Marlon Brandão de Sousa" <[EMAIL PROTECTED]>
Hello folks,
Some of you probably know me from the jawsscripting and
programmingblind discussion lists. For those of you who don't know me,
I am Marlon, from Brazil. I am a programmer, and a learning
intusiaste.
For several reazons, I am now starting to take a closer look at window
eyes. It seen to be a great screen reader, and I really need to learn
the new capabilities included with this great scripting feature.
I have a strong teorical and a good practical knowledge om JAWS
scripting, so every references I have of scripting concepts comes from
JAWS scripting.
I will need your help to start to stablish referenses and paralels
between the two concepts (WE and JAWS scripting), so I can start to
find my way through we scripting.
Please tell me if you're able to get this message, cinse the
subscription process was somehwat nebulous (I have not received a
message with instructions about how to post to the list, etc).
Thank you,
Marlon
--
When you say "I wrote a program that crashed Windows," people just
stare at you blankly and say "Hey, I got those with the system, for
free."
Linus Torvalds
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3423 (20080906) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
