yes, I know; I'm not advocating the .exe format in any way. it's only useful for someone who wants to write non-window-eyes scripts, and also, wants them encrypted. I was trying to make that clear (given that it's an advanced topic far beyond where we are in the class).
Chip -----Original Message----- From: Jared Wright [mailto:[email protected]] Sent: Thursday, March 10, 2011 6:12 AM To: [email protected] Subject: Re: VBSEdit You could encrypt the Window Eyes hosted scripts if you don't want the source code visible. On 3/9/2011 10:27 PM, Chip Orange wrote: > Hi Rick, > well, window-eyes would no longer be able to execute them with it's > built-in scripting engine; so yes, they would technically then become > an "external script", which would mean they would become more complex > to program than the vbs we're covering in class. also, much much more > tedious, as you have to type in a lot of stuff which window-eyes does > automatically supply for you when you use it's built-in scripting engine. > and since these are presumably specific to window-eyes, they offer no > advantage at all when made into an .exe (they aren't machine language, > so they wouldn't even run any faster), and they couldn't be executed > by a user without window-eyes. > unless of course you're not writing window-eyes scripts at all, but > more general scripts; then, the .exe only offers the slight advantage > that it hides your source code; but you can write general scripts > meant for non-window-eyes execution in a straight .vbs file, and it > would execute under any version of windows (as long as you don't care > that others can see your program code). > We will cover these differences a little further on in the class. > hth, > Chip > Chip > > ---------------------------------------------------------------------- > -- > *From:* RicksPlace [mailto:[email protected]] > *Sent:* Wednesday, March 09, 2011 8:00 PM > *To:* [email protected] > *Subject:* Re: VBSEdit > > I think the executables would be cool. But, would they be external > scripts to WindowEyes?In other words, I dont think they could be > loaded the same way as a text script in Script Manager but I'm not at all sure. > Rick USA > > ----- Original Message ----- > *From:* bT <mailto:[email protected]> > *To:* [email protected] <mailto:[email protected]> > *Sent:* Wednesday, March 09, 2011 4:36 PM > *Subject:* Re: VBSEdit > > Hi! > I thought you would like it and anyone interested in learning > vbscripting. > Chip had mentioned it off the cuff and it is worth the time to play > with it, especially the making of executable files for portability. > Bruce > *Sent:* Wednesday, March 09, 2011 1:47 PM > *Subject:* VBSEdit > > Hi VBS Guys: I also tried VBSEdit and like it allot so far. Line > numbers, Object Browser, Debugging, I couldn't use it yet, Snipets, > over 700 sample scripts and more like Intellisense that works well > with Windoweyes. The sample scripts and snipets cover just about > everything I can think of from ADO Database stuff and Sql Server > management and more to Computer internals listings and things I > don't even know what they are like remote thingys! > Note that I entered * the wildcard character asterik in the search > field under the Sample Scripts menu item in the search box. > For a beginner who knows a little about programming this looks like > a little gem of an application for developing a Windoweyes VBS script. > If you buy it you won't get that annoying pop up that comes up off > and on and then have to click the Evaluation button. > If you work with it too post up anything you find interesting. I > think I missed a few more nice features since I did not understand > them during my first fast run through. > Rick USA
