Thanks Ron: I have been looking for the best development environment. Vb.net
2008 got MTS errors I couldn't work around, VBS still looks good and I was
reading about JScript.net because it has access to the .net libraries yet
resides in a .js file which may, or not, run by just passing the .js file to
Windoweyes as an associated script like a.vbs file. The other thingy I have
read a little about was PowerShell which has access to the .net libraries but
neither .js nor Powershell are anything I know much about. What I am sort of
looking for is a language I can run like vbs by just associating them to an
application in Script Manager but still have access to all the goodies in the
.net libraries. Meantime I am moving ahead with VBS since that works well
enough and you guys have done allot of work on it already. Finally, I know you
are likely very busy with UIA ARIA and all that jazz. Seems like it would be a
quantum modification to implement with the core engine, scripting and
documentation so VBS is fine unless you have done something with .js or
something that uses the .net libraries. Even the WE Framework script would not
work without errors for me - likely doing something wrong. But, don't worry
about it. The whole new universe of UIA will be change enough and VBS does work
for now while experimenting with the WE Model as it now stands.
I just finished a small script and found out something about Intellisense which
is something I wanted to work with for a long time.
Rick USA
----- Original Message -----
From: Ron Parker
To: gw-scripting@gwmicro.com
Sent: Thursday, June 24, 2010 2:48 PM
Subject: Re: WSH and WindowEyes
On 6/24/2010 11:07 AM, RicksPlace wrote:
Hi: do scripts run under the WindowEyes Scripting Engine run under WSH
Not by default. If you package them in .wsf files then yes, they will run
under WSH in their own process. However, you'll find that when you do this, you
no longer have the predefined Application, Speech, and Script objects, though
you can at least predefine the Application object in the WSF headers. Also, you
have to follow the rules for external scripts: call ClientIdentify on startup
and watch for the OnShutdown event to stop your own execution.
or something else and, if so, what version?
They run in Window-Eyes. Window-Eyes creates an instance of whatever
ActiveScript engine your script needs, and passes your script to it. So if
you're running a VBScript script, Window-Eyes loads vbscript.dll (if it hasn't
already) and hands off the script to it.
Which version of VBScript (or whatever other ActiveScript engine) you're
running is up to your system. We run whatever's installed.
You might find this wiki article enlightening:
http://www.gwmicro.com/mediawiki/index.php/Internal_and_External_Scripts#Responsibilities_of_External_Scripts
