Userscripts.org

@The_Steph
I have identified where changes would need to be made but as yet have not settled upon the best values. I will see what can be done for the next release.

@sanriver12
The recent functional additions when disabled do not put any extra load on the script and use DOM nodes already identified for external links and the trackless option of the script.
Googlepreview works well for static pages of results but not for the autoload functionality available within GoogleMonkeyR. It seems some users were using GoogleMonkeyR, googlepreview and customizegoogle to get the effects i have included with about 20 lines of simple code (lines 512-531).
I had not added this functionality before because i could see no reason for it, others disagreed. I suggest you leave this new functionality disabled as i do.

mh

@The_Steph
I think i sort of get what you mean. If i'm following you correctly you want the site description text not to wrap and to use the whole cell width !? i.e. results wider with less height.

@Nasir Jones
Glad we got there in the end. It wasn't even that much coding !)

mh
P.S. if you are a fan of this code please "Favorite this script"

@Dave Piehl
You seem to be correct and the error comes from lastpass scanning the source of the iframe the GoogleMonkeR preferences loads in. The source of the preferences comes from a data:text/html;base64 coded string. Unfortunately there's no real (easy) way for me to do anything about this. See what lastpass say after all it's still in beta !)

@Cencio
Um. Opera. Fast, yes. My first choice, no.
At first glance Opera does not recognise tld's (top level domains) in the @source parameter of the meta data.
Then it doesn't have the built in functions GM_getData and such (fixable with an addin "Emulate GM Functions").
Then it produces a javascript error and doesn't tell you where it occurred.
I tried to load the built in debugger/DOM inspector (Dragonfly) and got a page cannot be found error.
I gave up. Sorry.

@Nasir Jones
With as much functionality as both GoogleMonkeyR and customizegoogle have in there own rite there are bound to be conflicts when they are both working on the same DOM. You found one. Exactly what functionality is missing from GoogleMonkeyR that you have in customizegoogle? You could always request a new GoogleMonkeyR feature !)

mh

@wolfgrrl
Thanks for the heads up, i honestly hadn't noticed it had stopped working! v1.0.8.9 should now auto-load more results correctly.

@dieslowly
The problem you're experiencing is due to several lines of code setting the style in "Google Search Sidebar for FF3..."
Basically this code uses pixel values for the main element widths (results and sidebar) and not something scalable like percentages

styles += '#searchPlus { overflow:hidden; margin:0 0 50px; float:right; width:320px; }';
needs changing to something like
styles += '#searchPlus { overflow:hidden; margin:0 0 50px; float:right; width:28%; }';

and

styles += '#res { width:600px; float:left; }';
change to
styles += '#res { width:70%; float:left; }';

That should do yah!
I'll leave it up to you to notify Kyle Day of these changes !)
regards
mh

P.S. some changes in v1.0.8.9 may have got rid of the crash when opening the preferences a second time. Please notify me either way as i still can't simulate it !(

@Name13013
I receive no income from this script what so ever! There are two donation links related to this script. One link on this page and one small link in the preferences window of GoogleMonkeyR. I receive no money from advertising and do not bump certain results higher in the results list. This code is free to use, copy and modify… just give credit where credit is due!

@NoOB123
Right, a good question! Well the coding structure uses JSON (JavaScript Object Notation). That being that var UIL = {…} creates an object with the properties and methods listed within the {} and assigns it to the variable UIL. The preferences screen is standard HTML that is shown in an iframe. The trick here is to encode the HTML in “data:text/html;base64” format that Firefox will automatically decode. Join all this together with binding of this to keep the persistence within the object and you have a script like GoogleMonkeyR… I’m sure that’s as clear as mud but you did ask!
mh

v1.0.8.8 another late night release !) They'll be the death of me!

@anonymous_user
I can only assume you mean the Google news results that always come first in the search results!? Yes i could build in a function and prefs to remove this result but feel its easier just to ask you to ignore them !)
As for the crash with FF3 with the prefs screen... i still can't reproduce it, so in turn, there's little chance of me fixing it.

If anyone else experiences this problem please let me know. Any pointers to where it could be coming from will be greatly received!

@Pierre75007
You're finding auto loading slow but would like me to build in functionality to bring back each results favicon... Which is it speed or pretty pictures? I know which i prefer! (even with asynchronous favicon calls you're still using precious bandwidth that could be returning your results.)

The age old problem of results pushing the screen so wide that scroll bars appear is a problem i'm loath to delve further into. Other than fixing results div widths and hiding the overflow within them, there is little i can do. Can i recommend you stick to two columns of results? Frankly i find more than two distracting and generally unnecessary anyway.

@sanriver12, @NoOB123, @Xymor, @Pierre75007 and @Marc Savoy
I do this for the love of it (but the beer fund could always do with a boost!)
Thanks for the thanks
I'll keep on doing it as long as i'm able.
mh

P.S. These long nights of coding would never be possible without the diamond tunes of http://www.friskyradio.com flowing though my speakers. If you like progressive dance give them a spin!