Good editor for VBScript?
in [VbScript]
|
From: Bob Barrows on 10 May 2010 15:17 MikeB wrote: > If, for instance I want InternetExplorer.application , do I have to > code > > Dim objIE > Set objIE = WScript.CreateObject("InternetExplorer.Application") > > IEobj = objIE > > and then if I type > > IEobj. (here I get intellisense?) No. For one thing, you did not use the SET keyword to point IEobj at the object referenced by objIE. I'm not sure why you would want to do that anyways. For another thing, Web-Ed does not have the capability to retrieve the needed information from the type library. > > Do I also have to do something in the Web-Ed settings? No. It's not a matter of changing a setting. It's a matter of writing the code to retrieve the information from the type library and compiling it into the Web-Ed program. -- HTH, Bob Barrows
From: Mayayana on 10 May 2010 15:32 > It seems that you spent more time showing how > VbsEdit works than > how to make Web-Ed do the same thing. It sounded like you wanted to keep it simple, so I figured that vbsEdit would make sense in that regard. It's clean, simple, and single-purposed, while also having very good intellisense. I agree with you that intellisense is a very big help -- and there are not many editors that provide it. > If, for instance I want InternetExplorer.application , do I have to code Dim objIE Set objIE = WScript.CreateObject("InternetExplorer.Application") IEobj = objIE and then if I type IEobj. (here I get intellisense?) Do I also have to do something in the Web-Ed settings? I tried doing something and then Web-Ed crashed. > Yikes! I haven't heard of anything like that. If you have the time I'd appreciate a private email about the details. Getting inellisense.... Hopefully you were able to make some sense of my earlier explanation, so you can see that an editor has to have information about an object in order to provide intellisense. In WEB-ED that's done by assigning variable names. 1) Open the auto-insert settings. (Icon on toolbar in vbs editor window.) 2) In upper right, enter ProgID (internetexplorer.application) or CLSID ({0002DF01-0000-0000-C000-000000000046} ). If you don't know either of those, you can also browse for the file. (For instance, MSHTML.TLB has the Document object typelib. There's no progid for that, and no creatable object. The object can be obtained through IE.Document, but it's not in the same typelib.) 3) Click "Info. from ProgID...." (or Browse) and a list of available objects will be returned. It shows all public objects, creatable or not, in the typelib. 4) Check the objects you want intellisense for, and click "Add Checked Objects". 5) That sub-window now closes and the Object List is again visible on the left. Select any object from there. (Rename it if you like.) In the textbox near the bottom enter a comma-delimited list of assigned variables. Then click "Update Variables". To update without closing WEB-ED, click "Reset All". 6) Close auto-insert settings. You can get intellisense for any object that way. You just have to know a ProgID, CLSID, or the file name for the typelib. IE is actually one of the sample objects that are set up by default. With that you just need to add the variable name you want to use. For instance, you might put: IE, ObjIE in the assigned variable names textbox. As for Vista/7 support, I support them, just not for most of my free software. I test the shareware on Vista/7, but with the free software I figured I needed to draw a line somewhere. A lot of people have trouble with permissions, UAC, virtualization, and Win32 vs Win64. Rather than have them writing to me to ask, "What's wrong with your DLL?" (without offering to pay me for my time) I decided it would be best just to design the free software not to run on Vista/7 at all. If you haven't already read it, there's an explanation here: http://www.jsware.net/jsware/ditips.php5#vist It's an awkward situation. As explained at that link, I don't think much of Vista/7. :) On the other hand, a lot of people have to use it or want to use it. I'd like to be helpful to those people. But nobody pays me for the components and free software. So in the final analysis, I just had to decide whether I was willing to spend my time doing Microsoft's tech. support for free. .....I'm not. > Then I looked around and I saw that you are reluctant to commit or provide support for Vista and Win 7 and I figure that it would not make sense to go any further. It is not as if I'm going to go back to XP or earlier releases. >
From: Bob Barrows on 10 May 2010 15:51 Mayayana wrote: > Hopefully you were able to make some sense of > my earlier explanation, so you can see that an editor > has to have information about an object in order to > provide intellisense. > In WEB-ED that's done by assigning variable names. > > 1) Open the auto-insert settings. (Icon on toolbar in > vbs editor window.) > > 2) In upper right, enter ProgID (internetexplorer.application) > or CLSID ({0002DF01-0000-0000-C000-000000000046} ). Oh, It appears the OP can ignore the second part of my reply. I was getting the impression from the earlier posts that WEB-ED was not given the ability to retrieve this information. It appears I came to the wrong conclusion. -- HTH, Bob Barrows
From: Mayayana on 10 May 2010 19:12 | Oh, It appears the OP can ignore the second part of my reply. I was | getting the impression from the earlier posts that WEB-ED was not given | the ability to retrieve this information. It appears I came to the wrong | conclusion. | Hmm. I wonder how many other people think that. :)
From: MikeB on 11 May 2010 08:29
On May 10, 2:32 pm, "Mayayana" <mayay...(a)invalid.nospam> wrote: >> Snipped for the sake of brevity. Hi and again thank you for the detailed reply. My recall is too hazy to be of any use on reporting to you the details of the Web-Ed crash. If it happens again I will try and find your email on your site ans send you a private note. As for Web-Ed Intellisense, I think I get it now. I have to tell Web- Ed the name of the variables that will be associated with the various objects. That's the part I didn't get. I'll try it out again, that doesn't seem to be too difficult. |