Chrome Extension Development, By Practical Example
github.com
github.com
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:
http://code.google.com/p/marking-menu-js/source/browse/#svn%...
Notice how it implements the important bits of Chrome's extension API in terms of Safari's:
http://code.google.com/p/marking-menu-js/source/browse/trunk...
That allows you to easily port Chrome extensions over.
https://github.com/atdt/chrome-force-media-type/blob/master/...
The Makefile might be interesting to you. It's very simple, but it automates an annoying part of the development cycle.
My extension is also on GitHub: https://github.com/cabin/linkhunter
https://github.com/tkahn6/hn-newcomments-chrome
And if you're interested in using it:
https://chrome.google.com/webstore/detail/kikfikaiccdaabdilg...
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.
"i find the readme scary. it encourages closing the web.
the rest's good - but - the intention's bad.