Writing Browser Extensions - Comparing Firefox, Chrome and Opera • Hacker News Board

Re: Writing Browser Extensions - Comparing Firefox, Chrome and Opera

#31

Post by aantix » Tue, Apr 10, 2012, 6:17 AM UTC

jaredsohn wrote: post #2

If you want to create a cross-browser extension, you can use an API such as Kynetx, Webmynd, CrossRider, or KangoExtensions. Links and pros/cons can be found here: http://stackoverflow.com/questions/4913123/cross-browser-ext...

I've been building an extension with Kango and so far everything has worked as advertised. The build process is a snap. Everything is written in Javascript; I have complete access to the DOM via Jquery. Builds for FF, Chrome and Opera. And their support has been quite responsive.

The only downside is that for IE build support you have to buy a commercial license which isn't cheap ($2500).

Re: Writing Browser Extensions - Comparing Firefox, Chrome and Opera

#32

Post by vetler » Tue, Apr 10, 2012, 8:59 AM UTC

Speaking of Opera, there's a labs release out that supports extensions on Opera Mobile: http://dev.opera.com/articles/view/extensions-opera-mobile-l...

Re: Writing Browser Extensions - Comparing Firefox, Chrome and Opera

#33

Post by zbuc » Wed, Apr 18, 2012, 8:31 PM UTC

rohitnair wrote: post #27

zbuc wrote: post #14

Earlier quoted context omitted.

NPAPI is difficult . I couldn't find a working sample project(though I only spent a couple hours) last year when I wanted to try it out. It sounds like Google is working on a new plugin architecture in JS + HTML that will support the deep interactivity of NPAPI, so we'll see...

Google already uses the new Pepper Plugin API[1] in the current versions of Chrome. They've also switched projects like Native Client to use this new API instead of NPAPI. PPAPI definitely seems better based on my experience of writing a few Native Client modules. [1] - http://code.google.com/p/ppapi/

Wow, good tip, thanks!