This is for all Greasemonkey developers who also use Firebug. Firebug is one of the best Firefox extension for developers.
To start with, almost every Greasemonkey developer uses built-in API method “GM_log()” to log debugging messages to Firefox’s javascript console.
While normal javascript developers use Firebug’s API method “console.log()” to log debugging messages to Firebug console.
Now problem is, if you try calling “console.log()” directly from Greasemonkey scripts, it will not work. As Firebug’s console object reside outside Greasemonkey scripts scope.
There are few workarounds to use Firebug console to log Greasemonkey debugging messages. But one which always work for me is detailed below.
Simplest way is to use…
unsafeWindow.console.log()
You can use other firebug logging functions similarly by prefixing unsafeWindow to them. Complete information about Firebug console can be found here.
Next what if you are editing your older Greasemonkey script! A simple way to use text-editors search-and-replace feature and replace all occurrences of “GM_log” with “unsafeWindow.console.log”.
Well it may be nice for some but geeks way is different! I will recommend adding following lines of code at the beginning of your Greasemonkey scripts.
if(unsafeWindow.console){
var GM_log = unsafeWindow.console.log;
}
The beauty of above codes is, it will first check if Firebug console is available. If yes, then all output from GM_log will be sent to Firebug console. And when Firebug is not available, it will simply use Firefox’s built-in javascript console without any error!
Next if you want to switch back to Firefox’s built-in javascript console, you can do that by just removing or commenting above code.
Disable logging for all GM_log calls…
While developing Greasemonkey scripts, we use GM_log a lot to speed-up coding. But once we are done, ideally we should remove all unnecessary GM_log calls from script as keep Firefox or Firebug console busy.
But this may not sound good idea for some guys who code scritps for sites which changes so often. So better approach is to disable logging via GM_log by adding one line of code, as below, in the beginning of script.
var GM_log = function (){};
This will basically assign an empty function to GM_log. Even smarter approach is to use code like below…
var GM_Debug = 0;
if(!GM_Debug) {
var GM_log = function(){};
}
Now all you have to change one character to enable/disable logging.
If you have noticed you are basically assigning a different function to GM_log to override it. Those who are new to javascript may find it little strange, but its perfectly valid!
