Skip to main content

Installing Userscripts in Firefox, Opera, Chrome

Want to install a userscript on your browser. Go no further. Here are simple instructions and caveats for installing Userscripts in Firefox, Opera, Chrome. If you want to author your own scripts, here is a beginner's tutorial.


Google Chrome:
imageChrome has built in support for userscripts from Chrome 4 release. All you have to do is to navigate to the userscript. Like from userscripts.org, or from a custom web hosted .user.js file, hit the link and you will see a warning (like below) to proceed cautiously. Scripts are auto managed under Tools>Extensions. You could update or delete them from chrome:extensions

Note: Not all userscripts work in Chrome. Chrome deliberately does not load @require and @resources entries from userscripts. So the author should have developed the script from a chrome user's perspective.

Firefox:

Although,userscripts saw the light of the day @ firefox first, Firefox still does not have a native support for them. You have to Install Grease Monkey extension. However all scripting features are available.

After that, it is similar to Chrome. Just navigate to the url of the .user.js file and Grease Monkey will pick it up and install it.

Advanced script management is provided by Grease Monkey extension. Manual available here

Opera:
Opera 11 also has built in support for userscripts. But installation and management is manual. You download the .user.js file manually and install in a specified folder. This folder location can be set under Settings > Advanced > Content > JavaScript Options. Manual here.

image    image

Some scripts might not work, although Opera makes every effort to full support of user scripts

Safari and Internet Explorer:

There seems to be no direct way to get userscripts to work in Safari or IE. But there is hope for hackers. Some 3rd party tools help you achieve the effect of userscripts. But you may have to run them at your own risk.

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

Decorator for Memcache Get/Set in python

I have suggested some time back that you could modularize and stitch together fragments of js and css to spit out in one HTTP connection. That makes the page load faster. I also indicated that there ways to tune them by adding cache-control headers. On the server-side however, you could have a memcache layer on the stitching operation. This saves a lot of Resources (CPU) on your server. I will demonstrate this using a python script I use currently on my site to generate the combined js and css fragments. So My stitching method is like this @memize(region="jscss") def joinAndPut(files, ext): res = files.split("/") o = StringIO.StringIO() for f in res: writeFileTo(o, ext + "/" + f + "." + ext) #writes file out ret = o.getvalue() o.close() return ret; The method joinAndPut is * decorated * by memize. What this means is, all calls to joinAndPut are now wrapped (at runtime) with the logic in memize. All you wa...

Faster webpages with fewer CSS and JS

Its easy, have lesser images, css and js files. I will cover reducing number of images in another post. But If you are like me, You always write js and css in a modular fashion. Grouping functions and classes into smaller files (and Following the DRY rule, Strictly!). But what happens is, when you start writing a page to have these css and js files, you are putting them in muliple link rel=style-sheet or script tags. Your server is being hit by (same) number of HTTP Requests for each page call. At this point, its not the size of files but the number server roundtrips on a page that slows your page down. Yslow shows how many server roundtrips happen for css and js. If you have more than one css call and one js call, You are not using your server well. How do you achieve this? By concatinating them and spitting out the content as one stream. So Lets say I have util.js, blog.js and so.js. If I have a blog template that depends on these three, I would call them in three script tags. Wh...