Hi Rick,
I downloaded VBS Editor and I actually like it. It is totally user friendly
with Windoweyes and even allows you to save an executable file of the program
you wrote in .VBS as a .exe file.
When running it there is a pop-up for registering but The selection is just
evaluate. For it is an unlimited usage of it each time you press the evaluate
button. This pop-up comes up when doing certain commands and the only annoying
thing about it I can tell so far.
So give it a try and to run your code just go to the debug menu.
It also allows you to save code in a folder inside the program. There is a
menu for saving objects, scripts, and you can make a new folder like I did for
classes. You also have the normal file menu where you can save it any place you
want. the other menu is for easy access and all code stored there is inside
compressed folders placed inside the documents user folder for applications
just like Windoweyes does for all its scripts. that folder is just in
compressed form, the only difference.
Just read the help menu on how to use it. It is very short and very easy to
use.
I think it would actually be a good program to use when testing and
debugging your programs. Give it a try and download it from the link below.
There is a 32 bit version and a 64 bit version.
Download:
http://www.vbsedit.com/
Bruce
----- Original Message -----
From: "RicksPlace" <[email protected]>
Sent: Monday, March 07, 2011 3:45 PM
Subject: Re: WE scripting class #3 in a few minutes
Thanks Bruce et al...
I used VB.net or VWD, think it was vwd to edit my vbs files. I had to make
them txt files and then I had a routine that would save or load that text
file from my Windoweyes folder where the scripts were actually saved. It
worked pretty well - line numbers being the best part of it. That said, it
is much easier to use notepad from within the Windoweyes Script manager
sometimes.
At least I think that is how it worked. I will try out NotePad again now
that I can use line numbers to find errors.
Thanks again...
Rick USA
----- Original Message -----
From: "bT" <[email protected]>
To: <[email protected]>
Sent: Monday, March 07, 2011 2:33 PM
Subject: Re: WE scripting class #3 in a few minutes
Hi Rick,
Yes, what Jeff said is correct. Making sure word wrap is off. Either
control G or alt-E-G and the line you are on pops-up.
All errors give the line number and all you have to do is go to that
line by entering it into that edit field which pops-up.
I don't bother with the larger editors, but they do have there
advantages because as one person pointed out, if you edit one file you can
also edit several files with the same update. That is OK if you are editing
many files.
But, I don't work on more than one file at a time. The adding of the
import method I wrote is my way of avoiding many files. Now since WE has its
own share method, that resolves many issues. You can write your own share
method and it is a little involved. I am sure that is what they did for WE
since VBScript has no shared method like visual basic has.
In my example of the sapi voices, I did it as a test. Those voices are
for writing stuff outside of WE but does offer a choice inside WE as well.
Sapi 4 voices are out-lawed by browser's because of memory leaks and viruses
which can be snuck in. It also does not do things the later versions do, but
the voices are neat and nice to have for games.
So, notepad is the easiest to use and does have its limitations.
Bruce
Sent: Monday, March 07, 2011 12:55 PM
Subject: RE: WE scripting class #3 in a few minutes
The nice thing about Notepad is that if Word Wrap is off, and show
status line is on, you can see your line number on the status line.
Also, you can use control-g to goto any line number.
Jeff Weiss
-----Original Message-----
From: RicksPlace [mailto:[email protected]]
Sent: Monday, March 07, 2011 10:47 AM
To: [email protected]
Subject: Re: WE scripting class #3 in a few minutes
Hi Bruce: What editor are you using that has line numbers? Chip is using
the
Office Product line which I don't have.
Rick USA
----- Original Message -----
From: "Chip Orange" <[email protected]>
To: <[email protected]>
Sent: Monday, March 07, 2011 8:11 AM
Subject: RE: WE scripting class #3 in a few minutes
> ok Bruce! great idea.
>
> Chip
>
>
> -----Original Message-----
> From: bT [mailto:[email protected]]
> Sent: Sunday, March 06, 2011 11:44 PM
> To: [email protected]
> Subject: Re: WE scripting class #3 in a few minutes
>
>
> Hi Chip,
>
> thanks for the info. I added my sapi45class and noticed the one
error
> on
> line 347where wscript was for the sapi4 sleep method. So, since WE
does
> not
> require the wscript and no object available, I added the on error
resume
> next and tested for err.number = 424 and just called the sleep method
and
> it
> works.
>
> So, my first test inside we worked fine despite the little hitch
which
> I
> cured.
>
> The little things inside we scripting that is different. Learn by
doing
> as they say.
>
> Bruce
>
> Sent: Sunday, March 06, 2011 9:49 PM
> Subject: RE: WE scripting class #3 in a few minutes
>
>
> fyi, the audio classes archive has been updated from tonight's class
and
> is
> at:
>
> http://acorange.home.comcast.net/scripting
>
> Chip
>
>
> -----Original Message-----
> From: Chip Orange [mailto:[email protected]]
> Sent: Sunday, March 06, 2011 6:54 PM
> To: [email protected]
> Subject: WE scripting class #3 in a few minutes
>
> just a reminder: today we'll actually get past some of the background
and
> write some small programs.
>
> Chip
>
> 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.
>
> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You
can
> manage your list subscription at http://www.gwmicro.com/listserv.
>
