62922 - Request for standalone plug-in SDK

Status: VERIFIED DUPLICATE of bug 90348

(Developer Documentation Graveyard :: General, defect, P2)

Description

[Tobias Trelle]

When will there be a standalone plug-in SDK for Mozilla that is
independent from the Moz source tree? Our wishlist for such an
SDK includes:

- a basic sample plug-in (with VS C++ workspaces)
- a sample for a scriptable plug-in
- xpidl binaries for major platforms
- LiveConnect --> XPConnect migration guide:
  "How to make Mozilla plug-ins scriptable?"
  (Thanks to the new XPCOM architecture scriptable
   plug-ins will have to be XPCOM components; so
   as a plug-in developer I'm forced to deal with
   XPCOM although I am not interested in it at all)

Comment 1

[John Vandenberg]

I have created a unix SDK that works with a mozilla binary release (presuming 
one can not write a plugin without being able to test it).  

It currently has a re-worked structured scriptable textbox plugin, and I am 
working on two others at the moment.  I was intending on posting it here in the 
next week or so for review, and hopefully so someone would make it cross-
platform.

As far as I know all binary releases include xpidl, thereby removing that 
requirement for the SDK, however not all unix platforms have uuidgen, so I have 
included the source.  

Comment 2

[Dan Mosedale (:dmosedale, :dmose)]

This seems like something Peter might have some thoughts about...

Comment 3

[av (gone)]

Standalone plugin example for Windows is in modules/plugins/mpdk. It has not 
been touched since M13, so it will require some tuning.

Comment 4

[Peter Lubczynski]

We really need this, perhaps first thing past post nsbeta1?

I'm working on a trying to get the old 4.x SDK to build me a XPCOM plugin 
in VC++ but it's a pain. 

upping priority and clearning milstone to re-evaluation

Comment 5

[Peter Lubczynski]

Andrei is working on this....

Comment 6

[av (gone)]

I am resolving this as a dup of 90348 as I posted first version there. Note that 
we are not promoting xpcom approach but rather recommend to stick with old NPAPI 
with some recent additions to it allowing scriptability and access the service 
manager.

*** This bug has been marked as a duplicate of 90348 ***

Comment 7

[rubydoo123]

catching up on verifications