Igor,
Is there a document that explains what this is and what it is for. In other
words: What does it mean to be a "scriptable interface", why do I need such a
thing and how do I use it (covert from what I currently have)?
The link you provided just seems to be an implementation.
In article <[EMAIL PROTECTED]>, Igor Kurshnirskiy says...
>
>Hello,
>
>Scriptable plugin API proposal is published for your review and
>evaluation.
>(http://lxr.mozilla.org/mozilla/source/java/plugins/wrappers/public/)
>
>The key thing about this proposal is that there is no need to change
>existing Plugin API.
>This is just set of interfaces and set of wrappers to bind new API to
>the old one.
>
>Following interfaces were scripted:
>nsIInputStream, nsIOutputStream, nsIPlugin, nsIPluginInstance,
>nsIPluginInstancePeer, nsIPluginManager, nsIPluginManager2,
>nsIPluginStreamInfo, nsIPluginStreamListener, nsIPluginTagInfo,
>nsIPluginTagInfo2
>
>Corresponding srciptable IDLs are
>nsIXPIDLInputStream.idl, nsIXPIDLOutputStream.idl, nsIXPIDLPlugin.idl,
>nsIXPIDLPluginInstance.idl, nsIXPIDLPluginInstancePeer.idl,
>nsIXPIDLPluginManager.idl, nsIXPIDLPluginManager2.idl,
>nsIXPIDLPluginStreamInfo.idl, nsIXPIDLPluginStreamListener.idl,
>nsIXPIDLPluginTagInfo.idl, nsIXPIDLPluginTagInfo2.idl
>.
>Not all methods are presented in the scriptable version of some
>interfaces.
>For example nsIXPIDLPlugin does not have setWindow method.
>
>C++ wrappers to bridge new API to the old one are available at
>http://lxr.mozilla.org/mozilla/source/java/plugins/wrappers/cpp/
>
>Who might be interested in such API.
>
>1. Any C++ plugin developer.
> It makes easier interthreading calls for plugins. (Because
>nsISupportsProxy will work with such API)
>2. Perl, Python, Java Script, ... developer.
> It makes possible to implement plugins in any language which has
>binding to xpcom.
>
>Thanks,
> Igor
>
