michaelfox + greasemonkey 70
User Scripts - The Chromium Projects
december 2010 by michaelfox
Chromium and Google Chrome (version 4 and higher) have built-in support for Greasemonkey-style user scripts.
To use, click on any .user.js file. You should see an install dialog. Press OK to install.
Known issues:
Chromium does not support @require, @resource, unsafeWindow, GM_registerMenuCommand, GM_setValue, or GM_getValue.
GM_xmlhttpRequest is same-origin only.
Match Patterns
The preferred way to specify the pages that a user script should run against in Chromium is the @match attribute. Here are some examples of its use:
// ==UserScript==
// @match http://*
// @match http://*.google.com/*
// @match http://www.google.com/*
// ==/UserScript==
See these comments for details on the @match syntax.
Support for Greasemonkey-style @include patterns is also implemented for compatibility, but @match is preferred.
With Greasemonkey-style @include rules, it is not possible for Chrome to know for certain the domains a script will run on (because google.* can also run on google.evil.com). Because of this, Chrome just tells users that these scripts will run on all domains, which is sometimes scarier than necessary. With @match, Chrome will tell users the correct set of domains a user script will run on.
chrome
javascript
userscripts
greasemonkey
wiki
reference
To use, click on any .user.js file. You should see an install dialog. Press OK to install.
Known issues:
Chromium does not support @require, @resource, unsafeWindow, GM_registerMenuCommand, GM_setValue, or GM_getValue.
GM_xmlhttpRequest is same-origin only.
Match Patterns
The preferred way to specify the pages that a user script should run against in Chromium is the @match attribute. Here are some examples of its use:
// ==UserScript==
// @match http://*
// @match http://*.google.com/*
// @match http://www.google.com/*
// ==/UserScript==
See these comments for details on the @match syntax.
Support for Greasemonkey-style @include patterns is also implemented for compatibility, but @match is preferred.
With Greasemonkey-style @include rules, it is not possible for Chrome to know for certain the domains a script will run on (because google.* can also run on google.evil.com). Because of this, Chrome just tells users that these scripts will run on all domains, which is sometimes scarier than necessary. With @match, Chrome will tell users the correct set of domains a user script will run on.
december 2010 by michaelfox
Use Google Web History Without Installing Google Toolbar
july 2010 by michaelfox
If you want to use Google Web History and save your browser's history on Google's servers, you generally need to go to this page and select "Enable Web History and install the toolbar". This procedure installs Google Toolbar, a plug-in available only for Internet Explorer and Firefox, and enables the PageRank feature, which displays the ranking of any site you visit while sending the URL to Google in the process.
If you use another browser or if you don't like Google Toolbar, there's an alternative way to send all the web pages you visit to Google: a script that asks Google for the PageRank of any web pages you load in your browser. To install the script you need:
* Greasemonkey, an extension for Firefox. Make sure to restart the browser before trying to add the script.
* Trixie, one of the best Greasemonkey-like plug-ins for Internet Explorer
* SIMBL and GreaseKit for Safari
* no additional software for Opera, but you need to enable the feature from Opera's interface
* Konqueror Userscript for Konqueror
The script is taken from this site, that also adapted it from other scripts. I mirrored the script to an easily-accessible location.
Once you've added the script, you only need to enable Google Web History: go to this page and select "Enable Web History and install the toolbar", but cancel the downloading process (you don't need the toolbar).
This feature only works when you're logged in to your Google Account. To disable it, remove the script from Greasemonkey or from another plug-in you've installed.
firefox
google
search
greasemonkey
userscript
history
tracking
lifelogging
track
If you use another browser or if you don't like Google Toolbar, there's an alternative way to send all the web pages you visit to Google: a script that asks Google for the PageRank of any web pages you load in your browser. To install the script you need:
* Greasemonkey, an extension for Firefox. Make sure to restart the browser before trying to add the script.
* Trixie, one of the best Greasemonkey-like plug-ins for Internet Explorer
* SIMBL and GreaseKit for Safari
* no additional software for Opera, but you need to enable the feature from Opera's interface
* Konqueror Userscript for Konqueror
The script is taken from this site, that also adapted it from other scripts. I mirrored the script to an easily-accessible location.
Once you've added the script, you only need to enable Google Web History: go to this page and select "Enable Web History and install the toolbar", but cancel the downloading process (you don't need the toolbar).
This feature only works when you're logged in to your Google Account. To disable it, remove the script from Greasemonkey or from another plug-in you've installed.
july 2010 by michaelfox
Conditional Logging - GreaseSpot
april 2010 by michaelfox
An even simpler option, retaining all of Firebug's console routines, and not interfering with additional parameters.
const DEBUG = 1;
if (!DEBUG) {
var console = {
log: function() {},
info: function() {},
warn: function() {},
error: function() {},
};
}
greasemonkey
userscripts
javascript
debug
console
firebug
firefox
logging
webdev
tools
snippets
code
browser
const DEBUG = 1;
if (!DEBUG) {
var console = {
log: function() {},
info: function() {},
warn: function() {},
error: function() {},
};
}
april 2010 by michaelfox
Jesse Ruderman » AutoLink user script
april 2010 by michaelfox
AutoLink turns plain text URLs, email addresses, bug numbers, ISBNs, and US phone numbers into links. For example, it turns all of these into links:
greasemonkey
regex
autolink
userscript
link
april 2010 by michaelfox
Location hack - GreaseSpot
april 2010 by michaelfox
The location hack is an ugly but useful way to interact with the content scope of the page being user scripted. It does this by indirectly evaling strings within that scope.
greasemonkey
userscripts
javascript
bookmarklets
april 2010 by michaelfox
related tags
addons ⊕ ajax ⊕ apps ⊕ autolink ⊕ autopagerize ⊕ bookmarklets ⊕ browser ⊕ browsing ⊕ calendar ⊕ chrome ⊕ code ⊕ command ⊕ console ⊕ convert ⊕ customization ⊕ data ⊕ debug ⊕ delicious ⊕ design ⊕ digg ⊕ dotjs ⊕ dropdown ⊕ email ⊕ embed ⊕ encoding ⊕ extension ⊕ extensions ⊕ facebook ⊕ firebug ⊕ firefox ⊕ firefox.ultimatesetup ⊕ flickr ⊕ fluid ⊕ generator ⊕ gist ⊕ github ⊕ gmail ⊕ GM_config ⊕ google ⊕ googlereader ⊕ greasemonkey ⊖ hacks ⊕ history ⊕ html ⊕ ical ⊕ information ⊕ install ⊕ instapaper ⊕ javascript ⊕ jquery ⊕ lifelogging ⊕ link ⊕ linkback ⊕ logging ⊕ mail ⊕ organization ⊕ parsing ⊕ pinboard ⊕ plugin ⊕ plugins ⊕ preferences ⊕ productivity ⊕ reader ⊕ reddit ⊕ reference ⊕ regex ⊕ resources ⊕ rss ⊕ scripts ⊕ search ⊕ shim ⊕ snippets ⊕ sync ⊕ template ⊕ textmate ⊕ tools ⊕ track ⊕ tracking ⊕ twitter ⊕ ui ⊕ ultimatebuild ⊕ uri ⊕ url ⊕ userscript ⊕ userscripts ⊕ video ⊕ web ⊕ webdev ⊕ wiki ⊕ youtube ⊕Copy this bookmark: