The first one that I absolutely need solved is how to get the plugin to
install.
What do I need to do to get Opera to recognize that it is missing the
plugin and download it?
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> I am porting my plugin from Firefox/Safari to Opera. The plugin
> mostly works, just down to two issues.
>
> The first one that I absolutely need solved is how to get the plugin
> to install.
>
> What do I need to do to get Opera to recognize that it is missing
> the plugin and download it?
Did you place your plug-in (.so file) in /usr/lib/opera/plugins/ this
is one of the directories that Opera searches for plugins.
Check /usr/share/opera/ini/pluginpath.ini -- this is a list of all
directories that Opera searches.
You can start Opera from the commandline w/ -debugplugin to ensure
that Opera is finding your plugin.
--
-rwf
Let me clarify a bit.
I am talking about a commercial product that has to install itself on our
end users computers. Because Opera is also used in many embedded devices
we expect to have quite a few users that have no idea what a command line
is as well as many users that do not have any command line or ability to
manually change the file system.
Now, on Firefox and IE our product brings up a dialog and the user clicks
install and the browser does the right thing. Safari is a pain because
all we can do is bring up a dialog that downloads a dmg and autolaunches
it. The installer in the dmg then walks the user through installation.
Is there anything in Opera that would work like this?
> On Tue, 15 Jan 2008 13:24:56 -0500, Robt. W. Fletcher Jr <m...@wa.us> wrote:
>
>> "Michael Rutman" <mo...@manicmoose.com> writes:
>>
>>> I am porting my plugin from Firefox/Safari to Opera. The plugin
>>> mostly works, just down to two issues.
>>>
>>> The first one that I absolutely need solved is how to get the plugin
>>> to install.
>>>
>>> What do I need to do to get Opera to recognize that it is missing
>>> the plugin and download it?
>>
>> Did you place your plug-in (.so file) in /usr/lib/opera/plugins/ this
>> is one of the directories that Opera searches for plugins.
>>
>> Check /usr/share/opera/ini/pluginpath.ini -- this is a list of all
>> directories that Opera searches.
>>
>> You can start Opera from the commandline w/ -debugplugin to ensure
>> that Opera is finding your plugin.
>>
>
> Let me clarify a bit.
My error. I 'assume' everybody runs GNU/Linux. ;-) I know squat about
any other OSs. Maybe somebody else will address your questions.
--
-rwf
> My error. I 'assume' everybody runs GNU/Linux. ;-) I know squat about
> any other OSs. Maybe somebody else will address your questions.
>
Well, that's a good starting point.
If you were to use Opera/Linux, a platform I'd like to support, how,
exactly, would you install our plugin?
With Firefox you would get a dialog asking you if you wanted to install
it. How does Opera work?
There is the 'pluginspage' attribute for the EMBED element:
http://msdn2.microsoft.com/en-us/library/ms534341(VS.85).aspx
... which is supported by Opera. If people click the plugin area, Opera
offers users to open that URL so they can download and install he plugin
themselves. The plugin installer then has to know how to find the various
plugin directories of the installed browsers from the registry, and places
the dll in those folders (on Windows).
How do you tell Firefox to install the plugin? Or are you talking about an
extension instead?
--
Rijk van Geijtenbeek
Opera Software ASA, Documentation & QA
Tweak: http://my.opera.com/Rijk/blog/