https://plusone.google.com/*
www.google.com##BUTTON[name="eswidget"]

Add-ons provide many useful features and functions, but they can also cause Firefox to become slower. Some add-ons can even slow Firefox to a crawl and make it difficult to use for regular web browsing. If you think add-ons might be the reason Firefox is lethargic, check the list below for some of the biggest bottlenecks. And remember, for best performance you should disable add-ons that you no longer use regularly.

Here are the reasons why someone would want to create a minimal firefox extension.

1. When you wish to create a local computer( disk) resident browser based application, interacting with the file system for reading and writing is possible if the application is structured as an extension.

2. Quick prototyping without worrying about XmlHttpRequest cross domain issues. When you run as plain application, user is hassled with a pop-up whenever XmlHttpRequest is attempted.

3. Many a times, installing an extension causes a lot of angst in terms of 'Will this mess up with my other customizations?'. A work in progress extension can be distributed along with a profile so that the user can preview, test it. Without worrying about messing with the default firefox browsing experience.

Here is a code to get you started with a minimal firefox extension bundled along with a user profile. The code comes with startup script(run.sh, run.bat)

Run your regular firefox browsing session and then run the startup script.( To avoid the feeling 'WTF, the stupid extension has messed up with my default firefox settings!?!' )

Vimperator is a Firefox browser extension with strong inspiration from the Vim text editor, with a mind towards faster and more efficient browsing. It has similar key bindings and you could call it a modal web browser, as key bindings differ according to which mode you are in. For example, it has a special Hint mode, where you can follow links easily with the keyboard only. Also most functionality is available as commands, typing :back will go back within the current page history, just like hitting the back button in the toolbar.

But Vimperator is more than just a simple command interface to Firefox — it is a complete development environment as well. If you are a web developer, you can enjoy an interactive JavaScript shell — even with completion support. Or if you want to extend Vimperator, you can easily do that by just dropping a JavaScript file in its plugin directory. Browse through our wiki pages for nice tips to customize Vimperator and for frequently asked questions. If you have more questions, you can visit us on IRC, in #vimperator on freenode.

his package contains the default CI system directory but with the following changes:

* CI_Router & CI_Loader classes merged with MY_ versions of Modular Seperation
* CI_Exceptions merged with the MY_ version of UhOh!
* CI's default DB replaced by RapidDataMapper (RDM)
* CI_Profiler and CI_Session were modified to work with RDM
* MP_Cache added to the system libraries
* A couple of default changes to the APP/config/config.php (like the base_url and compression on by default)
* A PHP5 autoloader which is loaded by the CI_Router class when available
* Default directories in APP folder for Exception classes, Abstract classes and interfaces (which are supported by the above autoloader)
* max() and min() functions were added to RDM's DB_Query_Select to return maximum and minimum values, work exactly the same as the count() function
* Objects and descriptors from RDM are "subfoldered" by changing underscores to dashes, so the class Page is in "data_model/page.php" and the class Shop_product is in "data_model/shop/product.php".
* AugmentedCI helper for an alternate CI syntax
* The comprehensive UhOh! errors are only shown to IP's added at the top of APP/config/config.php
* Default .htaccess for the main index.php
* Clean Controller and Models namespace (read more)

For a project at work we've been building a Firefox extension. It's slow, tedious work, with lots of time spent in the breakpointer functionality of Venkman. Thankfully Firefox extensions are basically javascript, and as I heard rumors of, you can embed jQuery inside of one.

How? Well it's quite simple. In your overlay.xul file, just include it like you would any other js file.
<script type="application/x-javascript" src="chrome://extensionname/content/jquery-1.2.6.min.js" />

Yup, that's it! Now you have access to all the usual jQuery functionality like element.click(), element.attr() and even the $.ajax calls, all within the scope of your extension. Thus, you can write extension code like this:
$('.toggle').attr('disabled', true);

Where it will select all XUL elements in your extension with the class toggle and set the disabled attribute to true.

If you want to have access to the browser DOM, you can access it via the document.defaultView attriute globally. Most times the defaultView variable is available inside of the event object if you've bound to one. Then, in order to effect the browser DOM, all you have to do is make use of the (often ignored) 2nd parameter of the $ function, the conext you'd like jQuery to work in.

In our case it's the browser's DOM. For example, to highlight all links on the page that are rel=nofollow, you just have to do this:
doc = document.defaultView;
jQuery("a[rel='nofollow']", doc).css({border: 'dotted 1px red', backgroundColor: 'pink'});

Now you have the power!