Discussion on GoogleMonkeyR | Userscripts.org

How to disable vertical outlining of search results in column view?, replied by Cerberus™

Cerberus™ — Fri, 13 Nov 2009 01:44:19 +0000

Thanks for your quick reply! If it was a lot of work to implement, I understand why you chose this layout. By the way, there also is the "Multi-Column Google Search" script, which does have two columns without the spacing issue; but it does not have all the other cool features and neat look of tha Monkey. Here it is; unfortunately I don't understand much of CSS scripting so I can't point out what exactly is the line or lines that does it:

// ==UserScript== // @name Multi-Column Google Search // @namespace http://userstyles.org // @description NEW version : http://userstyles.org/styles/647 // @author pawelkl // @homepage http://userstyles.org/styles/3730 // @include http://google.com/search* // @include http://google.pl/search* // @include http://www.google.com/search* // @include http://www.google.pl/search* // ==/UserScript==

non-Firefox support?, replied by gehav

gehav — Sun, 08 Nov 2009 20:31:12 +0000

Thanks a lot, mungushume! I just followed your instructions and now I can use your nice script not only in my Firefox installation but also in Opera!

Of course it would be nice if you change your mind and could provide possible future updates for Opera also :-)

Column width, replied by mungushume

mungushume — Wed, 04 Nov 2009 19:11:14 +0000

@Cerberus™
Not really sure what you're getting at here but line 465 implements the css code that determines how the results are displayed (up to a point). Playing with the values in here may get you what you want?!
mh

How to disable vertical outlining of search results in column view?, replied by mungushume

mungushume — Wed, 04 Nov 2009 19:06:50 +0000

@Cerberus™
Results are loaded into a table hence the spacing they get I.E. tallest cell denotes row height.
No getting around this easily
mh

non-Firefox support?, replied by mungushume

mungushume — Wed, 04 Nov 2009 19:04:38 +0000

@auscompgeek
It works fine for me on aagmfunctions.js v1.3.1 and opera v10.01

I guess it could be other scripts interfering or something else entirely. I don't really use opera so wouldn't know where to start looking on a user specific bug. i suggest you look at the error console and the developer plugin to track this problem down further.
mh

non-Firefox support?, replied by auscompgeek

auscompgeek — Mon, 02 Nov 2009 03:40:48 +0000

Err... yeah, clicking on the GoogleMonkeyR preferences link just greys out the page...

How to disable vertical outlining of search results in column view?, replied by Cerberus™

Cerberus™ — Sun, 01 Nov 2009 16:04:27 +0000

Brilliant script!
Q: I have my GoogleMonkey set to columns, and search results like this:
1 6
2 7
3 8
4 9
5 10
The results are vertically outlined: 1 and 5 start at the same hight, as do 2 and 6, et cetera. But when 1 is taller than 5, some space will be empty between 5 and 6 (see screenshot for extreme example of the space-wasting effect). Is there a way to disable vertical outlining? How could I edit the script to do it?

Privacy is an inherent human right!, replied by Cerberus™

Cerberus™ — Sun, 01 Nov 2009 15:43:27 +0000

I wonder why people use this Google toolbar at all. Using a bookmark with keyword is much better - unless I missed some advantage.

Column width, replied by Cerberus™

Cerberus™ — Sun, 01 Nov 2009 15:40:32 +0000

This is the best script for Google, and I've tried a lot.
Q: I'd like the search results to be a bit wider to save screen real estate: can I edit the script to accomplish that? I have tried changing getnumcol values a bit but it made no difference. This might however be due to interference with other scripts.

Column width, replied by mungushume

mungushume — Mon, 12 Oct 2009 17:08:51 +0000

@albo
Change line 460 of the script from if(UIL.Config.getNumCol()<5) to if(UIL.Config.getNumCol()>1)
That should give you the required result width
mh

Privacy is an inherent human right!, replied by mungushume

mungushume — Mon, 12 Oct 2009 17:01:15 +0000

What you're redirecting is an asynchronous call from the google toolbar to the loop back device.
How exactly would this slow down a page load in FF? It has nothing to do with the load time of the DOM and/or content.
mh

non-Firefox support?, replied by mungushume

mungushume — Mon, 12 Oct 2009 16:56:57 +0000

@auscompgeek
There a quite a few things that were causing it to fail, auto update code being part of it
Check out the file comparison to see what the others are

aagmfunctions.js gives access to all the necessary GM_ functions. Why would i need to define them? You can change the defaults in the script.

preferences dialogue failing???
mh

Privacy is an inherent human right!, replied by auscompgeek

auscompgeek — Mon, 12 Oct 2009 04:21:22 +0000

Some people run a web host on the loopback interface, and redirecting queries to the httpd running on the loopback interface would cause pages to load slower...
Use an invalid IP such as 255.255.255.0 as the IP to redirect to instead.
Firefox will detect the IP as invalid and won't try to load anything!

non-Firefox support?, replied by auscompgeek

auscompgeek — Mon, 12 Oct 2009 04:12:19 +0000

Ah, so the auto-update code was causing it to fail...

I already had aagmfunctions.js installed...

Could you define GM_... functions if they don't exist please? Add sensible defaults please (2 columns, number results, remove click tracking, auto load(?)...)

Wait a minute... the preferences dialog is failing...

Column width, replied by albo

albo — Sun, 11 Oct 2009 21:25:47 +0000

Hi There,

Would it be possible to add a setting to retain the original google results column width? When in one column mode, googlemonkeyr stretches the column width out, which makes the results more difficult to run down with your eyes.

thanks!

Some Features not working anymore, replied by gauravbaadshah

gauravbaadshah — Sun, 11 Oct 2009 08:36:39 +0000

Hi
Thanx for the update.
However, the preferences reset again every time I visit the Google search page after a browser restart.

Privacy is an inherent human right!, replied by mungushume

mungushume — Sat, 10 Oct 2009 13:38:00 +0000

Privacy is an inherent human right! Keep it!

The Google toolbar reports every page you visit back to http://toolbarqueries.google.tld where tld is is your google localisation i.e. in England it is co.uk
The Windows operating system contains a file called 'hosts' that will force redirection of domain names
The ip address 127.0.0.1 is called a loopback address and points to your own machine

This means that if in your hosts file you specify that toolbarqueries.google.tld should point to 127.0.0.1 the information which would report back to google gets sent no where

Here are some instructions on how to modify your hosts file

Open the hosts file
1, Go to the Start menu and choose Run. Type the following in the Run dialogue box:
For Windows NT and 2000: C:\winnt\system32\drivers\etc
For Windows XP / VISTA: C:\windows\system32\drivers\etc

2, Click the OK button

3, Find the file called 'Hosts' and double–click it. If prompted, specify that you would like to choose a program to open the file with from a list of programs. Choose 'Notepad' from the list of available programs.

4, Add the following lines to the hosts file

127.0.0.1 toolbarqueries.google.com
127.0.0.1 toolbarqueries.google.co.uk

if you use a different localisation then add that as well, save the file and restart your browser

Privacy is an inherent human right! Keep it!

Feel free to add your own comments

Version 1.3 will not work with google.co.uk, replied by Crisoco44

Crisoco44 — Sat, 10 Oct 2009 12:51:34 +0000

I have installed 1.3.1 but have to report that the same issue arises.
I always thought that my machine was reasonably powerful! It is certainly well above the average users specification.
Always seems to freeze when hitting the search button after entering a search word. There may be other factors involved but I do not know what they are.
Back to 1.2 again I am afraid for the timebeing.
I perhaps could try it with a very basic profile which I have set up. Later when I have time I will give this a try and report back.
Thank you for trying to sort it out.

---------------------------------------------------------------------

EDIT: I have checked out a basic Firefox profile with just GoogleMonkeyR installed and it works fine.
There is some inconsistency when the Google Filter Color script is enabled so it is not conclusive that this is causing the issue.
I was unable to determine what add-ons or scripts may have been causing this issue.

THIS IS MY WORKAROUND: 1.3.0 or 1.3.1
I have done away with the Google home page and I now load Google using Tab Mix Plus in a new tab with this address ......
http://www.google.co.uk/search?hl=en&q=+&btnG=S...=
This simply loads Google to a page with just the "search" box which has a space in the search box but without the "I'm Feeling Lucky" box.
Typing a search word after the space loads that search as normal with GoogleMonkeyR loaded. It also has none of the freezing that occurs when loading http://www.google.co.uk
The only disadvantage of course is that you lose the drop down search options as you type the word in the search box.
This also allows me to have the script Google Filter Color enabled so that I can also change the page background color as well as the results background color.

---------------------------------------------------------------------

EDIT 16-Oct-09

I have found that the above link with GoogleMonkeyR loaded causes Google Maps to freeze so if you are using this workaround it is necessary to directly open Maps with the following direct link and not use the button in the top left corner of the Google page .....
http://maps.google.co.uk/maps

Regards,
David

Version 1.3 will not work with google.co.uk, replied by mungushume

mungushume — Sat, 10 Oct 2009 11:42:41 +0000

@Crisoco44
After doing a little more testing i've identified an infinite loop that occurs with /webhp? home pages. I'm guessing the machine you're using is not the most powerful?! The loop is buffered with a delay of 100ms so most machines would cope fine. An updated version of the script can be found at the link below. Could you please install this and report your results?
Cheers
mh

http://google.monkeyr.com/ff/script/1.3.1/googl...

Version 1.3 will not work with google.co.uk, replied by Crisoco44

Crisoco44 — Fri, 09 Oct 2009 19:03:31 +0000

Hello mungushume.

Here are my results .......

Please answer the following
1, are you logged into a google account?
NO
2, do you have the google toolbar installed (not the ff built in search, the addon)?
NO Google Toolbar Installed.
3, version of ff?
3.5.3

So the problem is you can't actually type into the search dialogue???
NO! I CAN TYPE IN THE SEARCH BOX. IT WILL NOT PRODUCE RESULTS.
Very odd
1, load the page which is causing the problem
2, right click the GreaseMonkey icon at the bottom right of your browser. Left click GoogleMonkeyR to remove the tick next to it.
3, repeat step 2 for all other scripts that are trying to run on that url.
4, Refresh the page and see if the problem still exists.
5, If it works ok. re-enable GoogleMonkeyR and try again.
6, post results

DISABLING the script “Google Search – un-S-U-P-E-R-sized” clears the problem with GoogleMonkeyR enabled.

DISABLING “GoogleMonkeyR” and leaving “Google Search – un-S-U-P-E-R-sized” enabled also clears the problem.

The problem seems to be some incompatibility between the scripts “GoogleMonkeyR” version 1.3 only and “Google Search – un-S-U-P-E-R-sized”.

Incidentally it is very odd that when I hit "search" after entering a search word nothing happens but pressing F5 to refresh the page actually produces results for that word in GoogleMonkeyR. (with all scripts enabled). It also very strange that hitting "I'm Feeling Lucky" does actually search.

STRANGE> Sometimes its all working OK after refreshing the screen and then its back as it was again. Seems to be very temperamental.

EDIT: I have had to put back version 1.2 because the new version caused Firefox to crash once. Also I did further tests and found that the super size script is not affecting the problem. If I disable all my other scripts and just leave Monkey enabled then 1.3 will cause clicking the Google 'search' to not respond. I do not have that problem in version 1.2 or before and I am also able to use 'SUPER' script to revert back to the proper size of search box.
I know that Monkey will not load in the first Google page of results but like I said I shall have to put up with that for now.

Regards,
David

Version 1.3 will not work with google.co.uk, replied by mungushume

mungushume — Fri, 09 Oct 2009 16:54:55 +0000

@Crisoco44

Please answer the following
1, are you logged into a google account?
2, do you have the google toolbar installed (not the ff built in search, the addon)?
3, version of ff?

So the problem is you can't actually type into the search dialogue???
Very odd
1, load the page which is causing the problem
2, right click the GreaseMonkey icon at the bottom right of your browser. Left click GoogleMonkeyR to remove the tick next to it.
3, repeat step 2 for all other scripts that are trying to run on that url.
4, Refresh the page and see if the problem still exists.
5, If it works ok. re-enable GoogleMonkeyR and try again.
6, post results

Version 1.3 will not work with google.co.uk, replied by Crisoco44

Crisoco44 — Fri, 09 Oct 2009 15:49:50 +0000

Hello mungushume.
I thought I could see what the problem was.
If I open a new tab with http://www.google.co.uk and press enter then all is OK.
I had a new tab url set up to make version 1.2 work with the Google search box. It was
http://www.google.co.uk/webhp?hl=en&tab=iw
The search page looks exactly the same but it will not work with version 1.3
Further testing I find I still cannot get it to work even when starting with http://www.google.co.uk
Copy and paste or type in the search box will not respond at all.
I cannot understand it!
Later when I have time I will try switching off the SUPER size script to see if that solves it.
Refreshing the google search page seems to help.

Version 1.3 will not work with google.co.uk, replied by mungushume

mungushume — Fri, 09 Oct 2009 14:53:31 +0000

@Crisoco44
Can you confirm this is what you're doing?
1, Open a new tab in ff
2, type http://www.google.co.uk in the url bar. press enter
3, type a query in the the search box. press enter
4, nothing happens?

Is that what your doing? if not give me a step by step on what you are doing
also
1, are you logged into a google account?
2, do you have the google toolbar installed (not the ff built in search, the addon)?
3, version of ff?
mh

non-Firefox support?, replied by mungushume

mungushume — Fri, 09 Oct 2009 14:28:39 +0000

@auscompgeek

Right...
Opera support is a bit tricky as this script uses specific GM_ functions that do not exist in Opera
Here is a quick how to for use in Opera

1, Go http://www.howtocreate.co.uk/operaStuff/userJav... search for "Emulate GM functions". install this script in Opera.

2, Go http://google.monkeyr.com/opera/script/1.3.0/go... install this script in Opera.

As Opera does not allow cross site requests (cross site scripting) auto update and regular update are disabled.

To see the differences in the scripts go to http://pastebin.org/pastebin.php?diff=41189 "old version" is v1.3.0 for ff, "new version" is a modded version for Opera and "both versions" will show you the differences between the two.

I don't intend to keep an up-to-date Opera version for future revisions of the script so noting where changes have been made would be beneficial to anyone wanting to use Opera!
mh

Version 1.3 will not work with google.co.uk, replied by Crisoco44

Crisoco44 — Fri, 09 Oct 2009 14:10:44 +0000

Have upgraded from version 1.2 to version 1.3 but when I now apply a search from a clean Google.co.uk search box (bookmark) then nothing happens at all. Will work when I am already in GoogleMonkeyR but not when loading google.co.uk from a new tab bookmark.
I don't know if the script "Google Search - un-S-U-P-E-R-sized" is causing a conflict with version 1.3 but it means I now have to re-install version 1.2 again and suffer having to click back and forth between images and web to get GoogleMonkeyR to work.
I cannot work with the new larger text that Google has implemented so it means that script will have to stay.