Greasemonkey

Ryan Shaw: The key to survival will be going meta: design for the bright kids. Create a flexible, modular set of APIs and a well-documented example UI or two that shows how they are used. Learn from Amazon and release your grip on the end-user experience.  But developments like Greasemonkey disrupt more that just job descriptions: they disrupt business models too.

Here’s a directory of scripts.  For Safari users, check out PithHelmet Machete scripts.

My favorite example so far is Simon Willison’s msdn-platinfo.


My favourite so far is this one, which actually adds a new feature (persistent search folders) to GMail by hooking in to the already existing JavaScript functions on that site. Properly document them and you’ve got a JavaScript API.

Posted by Simon Willison at

Sam Ruby: Greasemonkey

Power to the people...

Excerpt from del.icio.us/tag/dhtml at


Hey, my wiki (and that script directory page) finally has a domain name.

Posted by Jeremy Dunck at

My favorite is LIP.

Posted by Mark at


I’d been thinking not long ago about how many sites don’t work with “non-standard” browsers for minor reasons and how it would be cool if there were a way to issue little patches for those sites until their maintainers got......

Excerpt from Coty's Weblog at


Programming in the browser…

Getting Unicode straight across platforms has been a huge hangup for me in trying to get together some tutorials on doing language processing with Python. And then, there’s another barrier to cross: how to deal with markup? Generally speaking, what...

Excerpt from infundibulum at

Add your comment












Nav Bar