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

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

Using Equinox CommandProvider to make OSGi console interactive.

After fiddling with the First Bundles that "Hello World"-ed upon Activation, You want to see more interactivity in OSGi. Although Using OSGi for an interactive Command Line Application would be like this one would be, well, a callable over-kill, I am going to start with an example and Expand it in later posts. So, please Welcome CommandProvider. CommandProvider is an EQUINOX specific API for extending the Console. This basic Example illustrates how to get a command from console and do something in java and also gets your feet wet on Service Registry package com.so.examples.commandconsole; import org. eclipse .osgi.framework.console .CommandInterpreter; import org.eclipse.osgi.framework.console.CommandProvider; public class DisplayMessageCommand implements CommandProvider { public void _say(CommandInterpreter ci) { ci.print("You said:" + ci.nextArgument()); } @Override public String getHelp() { return "\tsay - repeats what you say\n"; } }

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour