Chrome Extension Development, By Practical Example

The problem with extension development is that each browser does it differently.<p>If you abstract away the browser-specific API, it's not too hard to write a cross-browser extension. Here's one that runs on both Chrome and Safari:<p><a href="http://code.google.com/p/marking-menu-js/source/browse/#svn%2Ftrunk" rel="nofollow">http://code.google.com/p/marking-menu-js/source/browse/#svn%...</a><p>Notice how it implements the important bits of Chrome's extension API in terms of Safari's:<p><a href="http://code.google.com/p/marking-menu-js/source/browse/trunk/safari/hostAPI.js" rel="nofollow">http://code.google.com/p/marking-menu-js/source/browse/trunk...</a><p>That allows you to easily port Chrome extensions over.

Hey, cool! The source code for my Chrome extension is also on GitHub:<p><a href="https://github.com/atdt/chrome-force-media-type/blob/master/Makefile" rel="nofollow">https://github.com/atdt/chrome-force-media-type/blob/master/...</a><p>The Makefile might be interesting to you. It's very simple, but it automates an annoying part of the development cycle.

"Why Create a Chrome Extension?<p><pre><code> It's a great way to integrate seamlessly with a third-party site like Gmail. It in turn solves the "other site" problem, i.e., your customers don't want to go to yet another website. The Chrome Web Store is a wonderful source of traffic. All your friends are doing it.</code></pre> "<p>i find the readme scary. it encourages closing the web.<p>the rest's good - but - the intention's bad.