why does renaming a sample plugin cause a load failure?

[steve smith]

I need to write a scriptable plugin, so I started with the
npscriptable sample from the SDK and renamed the DLL (vcproj settings)
and the 'npscriptable' strings in the windows version resource
(npscriptable.rc)... thinking this would be the right thing to do...
and the plugin will not load.

If I build the npscriptable sample and copy that to the plugins
directory, it works fine.

I'm sure I'm missing something obvious, but I have been unsuccessful
so far... having tried many things.

If you have a pointer to another scriptable plugin sample, that would
be helpful as well.

thanks

[steve smith]

I guess I missed this in the documentation, but to prevent others from
struggling with this... your windows DLL name must start with "ns"...
for example, "np_myplugin.dll" or "npyippee.dll"

cheers

[Martin Husemann]

steve smith schrieb:

> I guess I missed this in the documentation, but to prevent others from
> struggling with this... your windows DLL name must start with "ns"...

> for example, "ns_myplugin.dll" or "nsyippee.dll"
>
I'm not sure I understood correctly what you are doing (or trying to
do), but you mean np*.dll, don't you?
Also "scriptable" sounds like you are on a wrong track, be sure to read
and understand the wikipedia article on NPRuntime
(http://en.wikipedia.org/wiki/NPRuntime#NPRuntime) and the blog series
starting here:
http://colonelpanic.net/2009/03/building-a-firefox-plugin-part-one/.

Martin