I think it's important the possibility to users add/edit/remove plugin
directories. So not only the default directories will be scanned. I
requested this function, but it was marked as WontFix, see:
http://code.google.com/p/chromium/issues/detail?id=29442
On 7 dez, 18:28, Peter Kasting <pkast...@google.com> wrote:
> Sigh, resending now that I have re-added my address to Groups after it got
> auto-removed :(
>
>
>
> On Mon, Dec 7, 2009 at 12:25 PM, Peter Kasting <pkast...@google.com> wrote:
> > On Mon, Dec 7, 2009 at 11:45 AM, Panayiotis Mavrommatis <
> > panayio...@google.com> wrote:
>
> >> I'm not sure if my email did reach chromium-dev,
>
> > It didn't, so I was confused at first :)
>
> > > > - Modify about:plugins for this purpose. That page is a simple
>
> > > > javascript page that iterates over navigator.plugins. Similar to
> >> other
> >> > > about: pages it doesn't have access to chrome internals. We feel
> >> > > chrome://plugins follows the model of chrome://extensions better,
> >> in that
> >> > > this page cannot be inspected and allows the user to modify state
> >> of the
> >> > > browser.
>
> > To users the distinction is meaningless. I suspect (but am not sure) that
> > we can write an internal handler that serves about:plugins in whatever way
> > we want (e.g. as a DOM UI page with two-way communication with the browser).
>
> > > > - Add the plugins to chrome://extensions -- we can do that too,
> >> we'll
> >> > > let Chromium devs chime in on what's the preferred option here.
>
> > We should definitely put the two together in whatever UI we end up with.
> > Users don't perceive these differently (just try explaining to a
> > non-developer how when they say "plugins" they really mean "extensions"),
> > and the information to see and actions to take are pretty much identical
> > with an extension versus a plugin.
>
> > > > - Modify mostly PluginService (chrome/browser/plugin_service.cc)
> >> > > - Will store state in the sqlite database, per user.
>
> > I'm not familiar with this code. Does it already use a sqlite database?
> > If not it might make sense to just shove this in the Preferences file.
> > This is where we list other similar data, and it avoids the overhead of
> > having another file to open and read on startup.
>
> > > > - A plugin is identified by its path in the filesystem. Different
> >> paths
> >> > > are considered different plugins.
>
> > Does this imply that different versions of a plugin are different plugins?
> > I ask because it would be annoying to find the Flash auto-reenabled itself
> > after it auto-updated. Perhaps "same name OR same path"?
>
> > PK
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
