🚀 go-pugleaf

On Thu, 29 Apr 1999 14:25:23 -0700, Richard Wilkman
<rwilkman@inprise.com> wrote:

>Chris:
>
>You don't really manage plug-ins.  They're installed on the client and
>fired off when requested.  IE has a much better mechanism for
>installing then Netscape.  Netscape usually just takes you to the web
>page for the company that has the plug-in.  You are on your own from
>there.

I know, but I WANT to manage them. :)  Not by fooling around with DLLs
in the plugin directory (which one is it?  is there more than one?
did something get installed in the system directory or another
application specific directory?) and not by fooling around with the
registry..

It's fine if there is a nice smooth plugin installation system (like
Netscape obviously DOESN'T have from my personal experience).  User
goes to page which requires a plugin.  Browser asks, "Do you want this
plugin?"  The browser downloads (after looking it up in a database),
installs and continues (no restart like Netscape, certainly not a
system restart).  From your description, this is what IE does.  Now if
I could determine which version I have installed, configure any plugin
specific settings (like which data types it will handle, many times
plugins compete for MIME types),  and remove a plugin -- then I would
be happy.

>But yes, once a plugin is installed (at least on WinTel) in one
>browser it is accessible by the other.

Are you sure about this?  Perhaps the browsers just seek out plugins
installed in other browsers.


Chris Hill
Chris244@aol.com