Jeff,
Yes, I figured a simple script would get F6 going back and forth.
Doug
Jeff Bishop wrote:
We need access to keys for getting to the output window and the object
browser. I emailed the author of the editor, we will see what he or
she says.
It could be scripted though probably.
Jeff
----- Original Message ----- From: "Doug Geoffray" <[email protected]>
To: <[email protected]>
Sent: Monday, February 01, 2010 1:05 PM
Subject: Re: VBSEdit
This really is cool and I think gives people that feel of an IDE.
The only thing you have to do is get used to us using the derived
Window-Eyes application object for it to work. Meaning instead of
just doing:
Speak "hello world"
you would have to do something like
we.speech.speak "hello world"
Which technically is more accurate but more work <grin>. So at the
beginning of all your scripts you would just do:
Set we CreateObject("WindowEyes.Application")
And then use we from there for everything. The ONLY thing you would
not have access to using with the we object you just got is the
Script object. Script is not derived from Application, it is just
given to an embedded script. So if you wanted something from the
Script object you would have to just use Script.blah which would of
course work fine but VBSEdit wouldn't know anything about it. Also,
what is so cool about VBSEdit is that even if you use variables for
objects it somehow keeps up. So things like:
Set mySpeech = we.Speech
mySpeech.
Would bring up the autocomplete to what the Speech object has. This
is very fast and more accurate then Aaron's FrameWork script.
FrameWork can't keep up with variable object names. I think if we
clean up the few things that don't speak (like the tooltip that pops
up) this really takes the wind out of not being a full IDE, at least
for writing the script in the editor.
Doug
Aaron Smith wrote:
It's pretty simply, really. Just add a reference to the wineyes TLB
(under Tools -> References), then create a WindowEyes.Application
object.
So do something like:
Set we = CreateObject("WindowEyes.Application")
Then, if you type w e period, the autocomplete list will pop up
showing all properties and methods of the Application object. The
only thing that doesn't seem to auto speak is the tooltip that pops
up when you start filling in the parameters of a method, for
example. But that could be scripted pretty easily, I beta.
Aaron
On 2/1/2010 2:01 PM, Jeff Bishop wrote:
How did you do that?
----- Original Message ----- From: "Aaron Smith" <[email protected]>
To: <[email protected]>
Sent: Monday, February 01, 2010 11:57 AM
Subject: VBSEdit
Greetings,
We recently played with an editor called VBSEdit, which is one of the
few designated VBScript editors. It's very accessible, and has a
built-in Intellisense/Autocomplete-like feature. We even added the
Window-Eyes OM to the autocomplete list for grins, and it actually
worked pretty well. So if you're interested, check it out:
http://www.vbsedit.com/
Aaron
--
Aaron Smith
Product Support Specialist * Web Development
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.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 GW
Micro Technical Support Team.
