Mark Miesfeld wrote: > I don't have a whole lot of help here. I really don't have much > understanding of how the scripting host is supposed to function, and > at one point I spent a lot of time trying to find examples and / or > documentation on it. > > A couple of comments that really are more to your original post > yesterday. It seems to me that: > > a.) Microsoft never expected people to write their own scripting host > engines. They expected people to script using the Microsoft provided > host engines. I say this because compared to their other > technologies, there is just no documentation on how to write a > scripting host engine. > There is a company, named ActiveState which has been producing WSH/ActiveX scripting engines for popular scirpting languages like Perl (a.k.a. Perlscript). AFAIK they have hired former Microsoft employees who have worked on WSH/ActiveX and therefore have been able to know all the ins and outs.
> b.) It seems to be a technology that Microsoft abandoned, or just let > drift away. I say that because they haven't done anything new with it > since the 90's. Sure they still support it, but they support in the > same way they still support using the 16-bit Windows APIs. > It is as dead or as alive as COM/OLE itself, IMHO. Microsoft has been trying hard to persuade everyone into .Net instead. However, it is reported that more than 50 % of the .Net efforts got invested in making the brdiging between COM/OLE and .Net as stable as possible, as too many customers have invested too heavily into COM/OLE. Actually, I would dub WSH/ActiveX to be a "mature technology", as it is at the heart of the MS InternetExplorer's DHTML for JSCript and VBScript. In addition it is the core technology for ASP AFAIK. These are also reasons, I think, why MS tried from the beginning to get it as stable as possible as early as possible as well. There may just be no reason to add anything new to it, as it serves already nicely its purpose. The WSH technology is also vital for scripting Windows itself (and there are mega-tons of scripts out there that use that part). [PowerShell is another attempt to allow for replacing that application area, but this will take decades as well.] The WSH is of strategic importance for the Windows platform, hence I think WSH will probably be around - like Windows itself - another twenty, thirty years or more. > That said, I do have a collection URLs pointing to things I found that > seemed most helpful. I send that to you in an e-mail so you can take > look at them. > A maybe helpful URL, that contains other interesting links: <http://en.wikipedia.org/wiki/Windows_Script_Host> with a lot of interesting downloads> ---rony ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
