Fair enough. I'll add it to the next version of the documentation.
Aaron
Chip Orange wrote:
ok, thanks Aaron. I do think it deserves a mention somewhere in the
documentation, as there's no way anyone would know what the object name
is to invoke window eyes.
Chip
------------------------------
Chip Orange
Database Administrator
Florida Public Service Commission
[EMAIL PROTECTED]
(850) 413-6314
(Any opinions expressed are solely those of the author and do not
necessarily reflect those of the Florida Public Service Commission.)
-----Original Message-----
From: Aaron Smith [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 23, 2008 1:19 PM
To: Chip Orange
Cc: [email protected]
Subject: Re: the we com automation server
Chip,
Once you have an object that points to the Window-Eyes
application, the
rest of the scripting manual applies (except for a few areas).
Presumably, if you are communicating through a COM interface to
Window-Eyes from an external source, you already know how to do that.
The Window-Eyes scripting documentation is directed as developers
creating hosted scripts.
That being said, we are in the process of creating some examples that
show how to communicate to Window-Eyes through external
applications, so
look for those soon on the Developer Resources (formerly
known as Script
Resources) on the Script Central website.
Also, you should join gw-scripting for all things script
related. Feel
free to ask any questions you have during your development process.
Aaron
Chip Orange wrote:
thank you Aaron for the info on:
CreateObject("WindowEyes.Application"), but there's a lot of extra
I want to be able to control window eyes from another app,
and I spent a
lot of time looking for this info in the scripting manual,
and couldn't
find it. Is it there?
thanks.
Chip
------------------------------
Chip Orange
Database Administrator
Florida Public Service Commission
[EMAIL PROTECTED]
(850) 413-6314
(Any opinions expressed are solely those of the author and do not
necessarily reflect those of the Florida Public Service Commission.)
-----Original Message-----
From: Aaron Smith [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 20, 2008 8:01 PM
To: Sam bushman
Cc: [email protected]
Subject: Re: the we com automation server
Sam,
As Jeff mentioned, Window-Eyes simply hosts the script files
for you so
that the entire Window-Eyes object model is available
immediately in
your scripts. You can run VBScript/JScript scripts without
Window-Eyes,
and access the Window-Eyes object model using
CreateObject("WindowEyes.Application"), but there's a lot of extra
overhead that you would need to manage, and it's just not
worth it.
That's why Window-Eyes does the hosting. It takes care of all that
overhead for you.
While you can certainly use VBScript and JScript, note that
any active
script engine that is supported by the Windows Scripting engine is
supported through hosted Window-Eyes scripts. In other words,
if you're
familiar with Perl, and use PerlScript (the Perl ActiveScript
engine),
you could write Window-Eyes scripts in PerlScript, and
they would run
just like VBScript or JScript scripts. The same goes for any other
ActiveScript language.
In addition, you can create external applications using C++,
or Visual
Basic, and access the Window-Eyes object model through them.
You still
have that overhead to deal with, but if you're writing
applications in
those languages, you're already familiar with how to take
care of all that.
I hope that helps.
Aaron
Sam bushman wrote:
Hi all,
I am trying to learn about the we com automation server.
I understand that it's built in to we 7.0.
I understand that it's either on / off or set to manual.
I understand that it can run vb script and jscript.
I understand that .vbs is the extention given to a text
file that is the
source for the scripts.
I understand that some scripts depend on other scripts to
be running to
enable them to use functions / objects that are already
defined and
available.
The we scripting engine is a com automation server that can
run these
scdripts.
It can start / stop them and expose the we API if you will to the
programmer.
Cool, got that!
Here is what I don't understand.
If I run a script ... I can use the we engine or I can use
the engine
that already comes with all of the latest versions of windows.
Since we now has a scripting engine how do I know that it
will not
conflict with the windows engine.
GW Micro did not replace the windows scripting engine with
the we com
automation server / scripting engine did they?
So could I use the windows engine / scripting host server
to run a
script and see the WE API?
What is the advantage to using the we scripting engine
and not the
windows scripting host?
I am just trying to understand how the we automation
server running
effects the main windows scripting host engine.
Thanks so much.
Sam Bushman
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will
receive it.
All GW-Info messages are archived at
http://www.gwmicro.com/gwinfo, and can be searched through
and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.
--
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 GW
Micro Technical Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support & Web Development
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will
receive it.
All GW-Info messages are archived at
http://www.gwmicro.com/gwinfo, and can be searched through
and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will
receive it.
All GW-Info messages are archived at
http://www.gwmicro.com/gwinfo, and can be searched through
and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.
--
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 GW
Micro Technical Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support & Web Development
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.
All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be
searched through and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.
--
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 GW
Micro Technical Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support & Web Development
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.
All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be
searched through and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.
