In article <[EMAIL PROTECTED]>, Sean Echevarria <[EMAIL PROTECTED]> wrote: > It's been awhile, but I think these were the rules I used: > > Restrict use of xpcom/utility macros (like NS_WITH_SERVICE, etc). > Don't use NS_IMPL_NSGETMODULE. > Don't use nsComPtr, getter_addrefs, etc. > > Roll your own nsIModule derived class. > Implement your own NSGetModule. > Use AddRef(), Release() and QueryInterface() directly. > > > On Mon, 03 Sep 2001 16:31:54 +0300, Mikael Himanka > <[EMAIL PROTECTED]> wrote: > > > >This sounds like a good idea. Can you go into more details? > >Implement the stuff from xpcom on the plugin itself, or copy-paste the > >needed stuff from mozilla source? > >How much and what code are we talking about? Here in plugin land we are interested creating a stand-alone XPCOM SDK which should allow you to use these convenience macros/nsCOMPtr/etc. w/o introducing link dependencies on XPCOM. We will release this as source code, so you can build static libraries yourself for this. We need an XPCOM SDK so that we can release a new plugin SDK that allows classic NP_API plugins to use just enough XPCOM to allow scripting and to use the service/component manager interfaces. Writing scriptable NPAPI plugins is documented here: http://www.mozilla.org/docs/scripting-plugins.html Watch this article for information about using the service manager. In short, we will providing a new variable enumeration to NPN_GetValue() so that a plugin can use the service manager. - Patrick
