I wouldn't recommend using NPAPI to do this either. The problem is
that it would involve editing files that are in-use by the browser,
which is dicey at best.
Erik
On Dec 29 2009, 3:42 pm, Rumith <jaffar.rum...@gmail.com> wrote:
> Thanks Brian, I'll look into the possibility of developing an NPAPI
> plugin.
>
> > The example functionality you list makes it
> > sound a lot like you want to re-create chrome://extensions/, though,
> > which seems superfluous.
>
> I aim to create an extension sync mechanism, much like the bookmark
> sync one. I haven't found such functionality in Chromium, and I
> believe that it would be a very convenient feature.
>
> On Dec 30, 2:13 am, Brian Kennish <bkenn...@chromium.org> wrote:> On Tue, Dec
> 29, 2009 at 2:27 PM, Rumith <jaffar.rum...@gmail.com> wrote:
> > > Reading the docs was the first thing I did :-) And yes, although there
> > > is an option for inter-extension messaging, I don't see there a way
> > > for even querying available extensions (aside from scraping
> > > chrome://extensions
> > > as you suggested).
>
> > Hey Rumith, scraping chrome://extensions/ isn't possible ("chrome"
> > isn't one of the schemes supported by content scripts). Given the
> > current extension API, I think a useful extension of this sort would
>
> Make sure you're adding real value before you
>
>
>
> > go down the NPAPI road — see the disclaimers in our documentation.)
--
You received this message because you are subscribed to the Google Groups
"Chromium-extensions" group.
To post to this group, send email to chromium-extensi...@googlegroups.com.
To unsubscribe from this group, send email to
chromium-extensions+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/chromium-extensions?hl=en.
