Re: XPCOM deprecation
Andrei Volkov <[email protected]>
| Newsgroups | gmane.comp.mozilla.devel.xpcom |
|---|---|
| Organization | Another Netscape Collabra Server User |
| Message-ID | <[email protected]> |
Leo Przybylski wrote:
> Hello,
>
> I'm trying to develop a netscape plugin. I was referred to use XPCOM with
> legacy Netscape plugins rather than use the XPCOM API because it may be
> gone tomorrow. Is that true? Why? Where can I get better information on
> legacy plugins? The current documentation on legacy plugins leaves much
> to be desired. Much of it appears to be inconsistent depending on where
> you get it.
>
> What should I do?
XPCOM plugin API is deprecated now. Developers are advised to use
NPAPI which is essentialy what is also known as legacy plugin API.
It is fully supported by Mozilla with the exeption of LiveConnect which
is no longer supported for plugin scriptability. However, scriptability
can be achived by other means (using XPConnect), also the browser service
manager is available for plugins so they can use public services.
The most recent documentation can be found on
http://mozilla.org/projects/plugins/ Please check periodically as new
articles are expected to be added.
New plugin SDK is a part of Mozilla tree and can be found under
modules/plugin/tools/sdk. Once build with the tree, it can be used
stand-alone.
Hope this helps.
I also think that you will get answers to plugin related questions
faster if you post to netscape.public.mozilla.plugins.
av