|
| Developed Mozilla-Plugin doesn`t work in Opera 9.0 |
 |
Wed, 28 Jun 2006 13:21:24 +020 |
Hi,
I am a plugin developer and I have to develop a vrml plugin for mozilla
browser ( with NPAPI ). So I have big problems with the new opera version
( 9.0 ).
Our developed plugin doesn`t run correctly with it, but it did with the 8.54
version.
I was able to debug something ( global functions ) and found out, that the
plugin is started right
( with functions
NPError NPP_New(NPMIMEType pluginType, NPP instance, uint16 mode, int16
argc, char* argn[], char* argv[], NPSavedData* saved)
NPError NPP_NewStream(NPP instance, NPMIMEType type, NPStream* stream,
NPBool seekable, uint16* stype)
}
but some plugin specific functions aren`t called by opera, e.g. functions
{
void NPP_StreamAsFile (NPP instance, NPStream* stream, const char* fname)
void NPP_URLNotify(NPP instance, const char* url, NPReason reason, void*
notifyData)
}
Are there any changes from version 8.54 to 9.0 in this context ?
Cheers,
Mariano
|
| Post Reply
|
| Re: Developed Mozilla-Plugin doesn`t work in Opera 9.0 |
 |
Wed, 28 Jun 2006 14:21:03 +020 |
"Mariano Spiegelberg" <m.spiegelberg@itnb-development.de>
writes:
> Hi,
>
> I am a plugin developer and I have to develop a vrml plugin for mozilla
> browser ( with NPAPI ). So I have big problems with the new opera version
> ( 9.0 ).
> Our developed plugin doesn`t run correctly with it, but it did with the
8.54
> version.
> I was able to debug something ( global functions ) and found out, that the
> plugin is started right
>
> ( with functions
> NPError NPP_New(NPMIMEType pluginType, NPP instance, uint16 mode, int16
> argc, char* argn[], char* argv[], NPSavedData* saved)
>
> NPError NPP_NewStream(NPP instance, NPMIMEType type, NPStream* stream,
> NPBool seekable, uint16* stype)
>
> }
>
> but some plugin specific functions aren`t called by opera, e.g. functions
>
> {
> void NPP_StreamAsFile (NPP instance, NPStream* stream, const char* fname)
>
> void NPP_URLNotify(NPP instance, const char* url, NPReason reason, void*
> notifyData)
>
> }
>
> Are there any changes from version 8.54 to 9.0 in this context ?
>
> Cheers,
> Mariano
Not specifically, but with the implementation of the 0.16 api (i.e.
the scripting api) there have been quite some changes to the
internals, so there may be some fallout. If we do not behave
according to the specification, please file a bug report
(https://bugs.opera.com/wizard/). If you can give us something that
makes it easier for us to reproduce the problem, that would certainly
be preferable :)
"Mariano Spiegelberg" <m.spiegelberg@itnb-development.de>
writes:
> Hi ,
>
> are there still the problems with Scriptable Plugins ( Communication
<=>
> Plugin ) or can Opera handle this kind of plugins and have a full-support
> for that ?
>
> Cheers,
> Mariano
We are supposed to have support for the JavaScript interface (NPObject
and friends) now. I don't think it has been extensively tested, since
there aren't that many plug-ins that use this interface.
I know the unix-specific elements have not been tested at all, and I
would really like to do so. But I don't know of any plug-ins using
this interface on unix.
|
| Post Reply
|
| Re: Developed Mozilla-Plugin doesn`t work in Opera 9.0 |
 |
Wed, 28 Jun 2006 15:01:04 +020 |
> please file a bug report
Yes, I did.... thank you for that info. I hope there are opera developer who
can help...
> We are supposed to have support for the JavaScript interface (NPObject
> and friends) now. I don't think it has been extensively tested, since
> there aren't that many plug-ins that use this interface.
What I want is to use easily the developed JavaScript-Interface in the form
of XPCOM.
That`s a common way and needs the components folder, but it still isn`t in
opera folders....
Or did I understood something wrong ??
Cheers,
Mariano
"Eirik Byrkjeflot Anonsen" <eirik@opera.com> schrieb im
Newsbeitrag
news:87hd25tqs0.fsf@opera.com...
> "Mariano Spiegelberg" <m.spiegelberg@itnb-development.de>
writes:
>
>> Hi,
>>
>> I am a plugin developer and I have to develop a vrml plugin for
mozilla
>> browser ( with NPAPI ). So I have big problems with the new opera
version
>> ( 9.0 ).
>> Our developed plugin doesn`t run correctly with it, but it did with the
>> 8.54
>> version.
>> I was able to debug something ( global functions ) and found out, that
>> the
>> plugin is started right
>>
>> ( with functions
>> NPError NPP_New(NPMIMEType pluginType, NPP instance, uint16 mode,
int16
>> argc, char* argn[], char* argv[], NPSavedData* saved)
>>
>> NPError NPP_NewStream(NPP instance, NPMIMEType type, NPStream* stream,
>> NPBool seekable, uint16* stype)
>>
>> }
>>
>> but some plugin specific functions aren`t called by opera, e.g.
functions
>>
>> {
>> void NPP_StreamAsFile (NPP instance, NPStream* stream, const char*
fname)
>>
>> void NPP_URLNotify(NPP instance, const char* url, NPReason reason,
void*
>> notifyData)
>>
>> }
>>
>> Are there any changes from version 8.54 to 9.0 in this context ?
>>
>> Cheers,
>> Mariano
>
>
> Not specifically, but with the implementation of the 0.16 api (i.e.
> the scripting api) there have been quite some changes to the
> internals, so there may be some fallout. If we do not behave
> according to the specification, please file a bug report
> (https://bugs.opera.com/wizard/). If you can give us something that
> makes it easier for us to reproduce the problem, that would certainly
> be preferable :)
>
>
> "Mariano Spiegelberg" <m.spiegelberg@itnb-development.de>
writes:
>
>> Hi ,
>>
>> are there still the problems with Scriptable Plugins ( Communication
<=>
>> Plugin ) or can Opera handle this kind of plugins and have a
full-support
>> for that ?
>>
>> Cheers,
>> Mariano
>
> We are supposed to have support for the JavaScript interface (NPObject
> and friends) now. I don't think it has been extensively tested, since
> there aren't that many plug-ins that use this interface.
>
> I know the unix-specific elements have not been tested at all, and I
> would really like to do so. But I don't know of any plug-ins using
> this interface on unix.
>
>
> eirik
|
| Post Reply
|
| Re: Developed Mozilla-Plugin doesn`t work in Opera 9.0 |
 |
Wed, 28 Jun 2006 16:43:06 +020 |
"Mariano Spiegelberg" <m.spiegelberg@itnb-development.de>
writes:
>> please file a bug report
>
> Yes, I did.... thank you for that info. I hope there are opera developer
who
> can help...
>
>> We are supposed to have support for the JavaScript interface (NPObject
>> and friends) now. I don't think it has been extensively tested, since
>> there aren't that many plug-ins that use this interface.
>
> What I want is to use easily the developed JavaScript-Interface in the form
> of XPCOM.
> That`s a common way and needs the components folder, but it still isn`t in
> opera folders....
> Or did I understood something wrong ??
>
>
> Cheers,
> Mariano
>
I don't really know what XPCOM is, but I have the impression that it
is very much a mozilla-specific interface. In that case, I doubt that
we support it.
eirik
>
>
> "Eirik Byrkjeflot Anonsen" <eirik@opera.com> schrieb im
Newsbeitrag
> news:87hd25tqs0.fsf@opera.com...
>> "Mariano Spiegelberg"
<m.spiegelberg@itnb-development.de> writes:
>>
>>> Hi,
>>>
>>> I am a plugin developer and I have to develop a vrml plugin for
mozilla
>>> browser ( with NPAPI ). So I have big problems with the new opera
version
>>> ( 9.0 ).
>>> Our developed plugin doesn`t run correctly with it, but it did with
the
>>> 8.54
>>> version.
>>> I was able to debug something ( global functions ) and found out,
that
>>> the
>>> plugin is started right
>>>
>>> ( with functions
>>> NPError NPP_New(NPMIMEType pluginType, NPP instance, uint16 mode,
int16
>>> argc, char* argn[], char* argv[], NPSavedData* saved)
>>>
>>> NPError NPP_NewStream(NPP instance, NPMIMEType type, NPStream*
stream,
>>> NPBool seekable, uint16* stype)
>>>
>>> }
>>>
>>> but some plugin specific functions aren`t called by opera, e.g.
functions
>>>
>>> {
>>> void NPP_StreamAsFile (NPP instance, NPStream* stream, const char*
fname)
>>>
>>> void NPP_URLNotify(NPP instance, const char* url, NPReason reason,
void*
>>> notifyData)
>>>
>>> }
>>>
>>> Are there any changes from version 8.54 to 9.0 in this context ?
>>>
>>> Cheers,
>>> Mariano
>>
>>
>> Not specifically, but with the implementation of the 0.16 api (i.e.
>> the scripting api) there have been quite some changes to the
>> internals, so there may be some fallout. If we do not behave
>> according to the specification, please file a bug report
>> (https://bugs.opera.com/wizard/). If you can give us something that
>> makes it easier for us to reproduce the problem, that would certainly
>> be preferable :)
>>
>>
>> "Mariano Spiegelberg"
<m.spiegelberg@itnb-development.de> writes:
>>
>>> Hi ,
>>>
>>> are there still the problems with Scriptable Plugins (
Communication <=>
>>> Plugin ) or can Opera handle this kind of plugins and have a
full-support
>>> for that ?
>>>
>>> Cheers,
>>> Mariano
>>
>> We are supposed to have support for the JavaScript interface (NPObject
>> and friends) now. I don't think it has been extensively tested, since
>> there aren't that many plug-ins that use this interface.
>>
>> I know the unix-specific elements have not been tested at all, and I
>> would really like to do so. But I don't know of any plug-ins using
>> this interface on unix.
>>
>>
|
| Post Reply
|
| Re: Developed Mozilla-Plugin doesn`t work in Opera 9.0 |
 |
Wed, 28 Jun 2006 17:22:40 +020 |
> I don't really know what XPCOM is, but I have the impression that it
> is very much a mozilla-specific interface. In that case, I doubt that
> we support it.
Yes, it`s an important part of the mozilla plugin interface. So I think
Opera doesn`t support mozilla plugins entirely - what a pity....
But I don`t want to loose the hope....
"Eirik Byrkjeflot Anonsen" <eirik@opera.com> schrieb im
Newsbeitrag
news:87zmfxs5mt.fsf@opera.com...
> "Mariano Spiegelberg" <m.spiegelberg@itnb-development.de>
writes:
>
>>> please file a bug report
>>
>> Yes, I did.... thank you for that info. I hope there are opera
developer
>> who
>> can help...
>>
>>> We are supposed to have support for the JavaScript interface
(NPObject
>>> and friends) now. I don't think it has been extensively tested,
since
>>> there aren't that many plug-ins that use this interface.
>>
>> What I want is to use easily the developed JavaScript-Interface in the
>> form
>> of XPCOM.
>> That`s a common way and needs the components folder, but it still isn`t
>> in
>> opera folders....
>> Or did I understood something wrong ??
>>
>>
>> Cheers,
>> Mariano
>>
>
> I don't really know what XPCOM is, but I have the impression that it
> is very much a mozilla-specific interface. In that case, I doubt that
> we support it.
>
> eirik
>
>
>
>>
>>
>> "Eirik Byrkjeflot Anonsen" <eirik@opera.com> schrieb im
Newsbeitrag
>> news:87hd25tqs0.fsf@opera.com...
>>> "Mariano Spiegelberg"
<m.spiegelberg@itnb-development.de> writes:
>>>
>>>> Hi,
>>>>
>>>> I am a plugin developer and I have to develop a vrml plugin for
mozilla
>>>> browser ( with NPAPI ). So I have big problems with the new
opera
>>>> version
>>>> ( 9.0 ).
>>>> Our developed plugin doesn`t run correctly with it, but it did
with the
>>>> 8.54
>>>> version.
>>>> I was able to debug something ( global functions ) and found
out, that
>>>> the
>>>> plugin is started right
>>>>
>>>> ( with functions
>>>> NPError NPP_New(NPMIMEType pluginType, NPP instance, uint16
mode, int16
>>>> argc, char* argn[], char* argv[], NPSavedData* saved)
>>>>
>>>> NPError NPP_NewStream(NPP instance, NPMIMEType type, NPStream*
stream,
>>>> NPBool seekable, uint16* stype)
>>>>
>>>> }
>>>>
>>>> but some plugin specific functions aren`t called by opera, e.g.
>>>> functions
>>>>
>>>> {
>>>> void NPP_StreamAsFile (NPP instance, NPStream* stream, const
char*
>>>> fname)
>>>>
>>>> void NPP_URLNotify(NPP instance, const char* url, NPReason
reason,
>>>> void*
>>>> notifyData)
>>>>
>>>> }
>>>>
>>>> Are there any changes from version 8.54 to 9.0 in this context
?
>>>>
>>>> Cheers,
>>>> Mariano
>>>
>>>
>>> Not specifically, but with the implementation of the 0.16 api
(i.e.
>>> the scripting api) there have been quite some changes to the
>>> internals, so there may be some fallout. If we do not behave
>>> according to the specification, please file a bug report
>>> (https://bugs.opera.com/wizard/). If you can give us something
that
>>> makes it easier for us to reproduce the problem, that would
certainly
>>> be preferable :)
>>>
>>>
>>> "Mariano Spiegelberg"
<m.spiegelberg@itnb-development.de> writes:
>>>
>>>> Hi ,
>>>>
>>>> are there still the problems with Scriptable Plugins (
Communication
>>>> <=>
>>>> Plugin ) or can Opera handle this kind of plugins and have a
>>>> full-support
>>>> for that ?
>>>>
>>>> Cheers,
>>>> Mariano
>>>
>>> We are supposed to have support for the JavaScript interface
(NPObject
>>> and friends) now. I don't think it has been extensively tested,
since
>>> there aren't that many plug-ins that use this interface.
>>>
>>> I know the unix-specific elements have not been tested at all, and
I
>>> would really like to do so. But I don't know of any plug-ins
using
>>> this interface on unix.
>>>
>>>
>>> eirik
|
| Post Reply
|
|
|