Could someone please clarify the comments below: Do they mean that Javascript in a web page displayed by Mozilla can create and use arbitrary ActiveX objects, as with JScript's ActiveXObject? The main XPConnect page seems to say otherwise, but if that's out of date I'd like to know where I can find more up to date info.
I've had trouble making an XPCOM component that wraps IDispatch, and it would be nice to find out that I don't need to bother. Myles Williams "Benjamin Smedberg" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Jon Smirl wrote: >> On 3/3/06, Christian Biesinger <[EMAIL PROTECTED]> wrote: >>> Emanuel Dejanu wrote: >>>> 1. I want to develop an application that will be able to export objects >>>> as XPCOM or COM. Is there a layer for this. So that I write a single >>>> code >>>> and with a define I can get XPCOM or COM objects. >>> The actual COM and XPCOM objects are compatible. I.e., all you should >>> need to change is the registration code. >> >> Does XPCOM offer dual interfaces on windows or do you need to use >> invoke for everything? > > XPCOM has no concept of IDispatch: scripting (xpconnect) is implemented by > inspecting the type library and coercing arguments into the correct form > to call on the interface. XPConnect does also support scripting of > IDispatch directly for MSCOM compatibility. > > --BDS Jeremy E wrote: > Does that mean that I can create any COM object on Windows from my > extension using script? I think so, as long as the component supports IDispatch. It might require some special prefs to be enabled. I don't really know the details. --BDS _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
