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

One page Stock

Alright.. That was a long absence. The whole last week I dint blog. I dint go away. I was "occupied". I was learning stock trading. Its very fascinating. I have a good weeeked blog for you all. Here is my experience. I can literally hyper-link every word from the following paragraphs, but I am writing it as simple as I can so you can look up the italicised words in wikipedia . I got a paper trading account from a brokerage firm . You need one brokerage account first. Then it can be an Equity account where all your money is yours or a Margin account , where some of the money is lent by the brokerage firm. Then I get Buying power , which is the dollor value of how much stocks you can buy. I can make profit by simple rules. Buy when Price is low. Sell when price is high. There is another more intersting way of earning money. Selling short . Thats when price is not high, per say, but when are confident that the price WILL go down. then buy back when its lowest. This is what

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>