Could Cache Listing indicate if Found by viewer?

[+padlinfool]

I thought it would be nice if the Cache Listing page could indicate if it was already found by the logged on user.

 

A big Red Check or Smiley Icon prominently displayed somewhere on the page would be great.

 

Right now we have to scroll down through the logs to find our found log or open Geocaching.com Google Maps to find a smiley. I'm sure there are other ways also.

[+renruts]

If you use Firefox as your browser, there are several very nice Greasemonkey scripts out there to modify teh look and feel of the page for you and one of them does just that.

[+mtn-man]

Here is one of the Greasemonkey/Firefox scripts that work great.

 

http://gmscripts.locusprime.net/Totals_By_Log_Type.html

[+Tequila]

Seems it would be simpler if gc.com would make the change once and everyone could enjoy it. Including IE users.

[+mtn-man]

The site over time has added some of these enhancements into the site. A prime example is shown on the page I linked in fact. Prime Suspect built a script to show the totals based on the log types and this was displayed right over the logs. GC.com eventually added that feature, rendering Prime's script redundant. Maybe this could be added at some point.

[+BigCarbonFootprint]

I thought it would be nice if the Cache Listing page could indicate if it was already found by the logged on user.

 

A big Red Check or Smiley Icon prominently displayed somewhere on the page would be great.

 

Right now we have to scroll down through the logs to find our found log or open Geocaching.com Google Maps to find a smiley. I'm sure there are other ways also.

 

The feature you request used to be available on GC.com at the top right of the listing page. I have noticed over the last year or so this function has disappeared. Bummer, I found it very handy.

[+Lil Devil]

Here is one of the Greasemonkey/Firefox scripts that work great.

 

http://gmscripts.locusprime.net/Totals_By_Log_Type.html

That script was broken by a recent site update. Try this script instead, which does everything the old script did, and much more

[+mtn-man]

Awesome! I thought it was just me and another Vista problem. Sweetness!

[+trainlove]

Not everyone uses one kind of web browser.

I think this would be a great feature for all cachers.

 

I've asked for it before, and an answer was, well didn't you see a checkmark next to the cache name on the previous page? But the way I got to the cache page was not through a search so NO there was no page where a checkmark could be shown, except for the completely logical request of this OP on the cache page itself.

 

I also think another, exactly similar request, would be for travel bug pages to show that you have 'grabbed', 'retrieved' or 'discovered' that bug, and not force you to have to page through 20 or more pages of logs on that bug. And of course, why doesn't a list of bugs, such as all the Alien geocoins owned by cacherxyz, not have a checkmark for those that you have logged? Same code that's used on a cache search page, right?

 

travel bugs and geocoin web pages get the short end of the stick when it comes to feature requests (usually) on groundspeak. Perhaps part of the popularity behind PathTags,

Edited October 25, 2008 by trainlove

[+Kabuthunk]

Eh. I just open the list of all cache logs, and you can just hit CTRL+F and search for it, if your list is too long to just scroll through quickly. Takes a slightly longer time, but if you have it bookmarked, it's a LOT faster than having to open a specific cache page, and then click on 'view all logs' and wait for the now longer-loading page to load.

[+padlinfool]

Many times we get to cache pages from notification emails. We see a cache find or DNF and wonder if we have it already. As our find list grows longer, our memory seems to get shorter. This "Found" feature would be great. If this info was an added comment on the notification email that would also be handy!

 

also..

 

The greasemonkey script works GREAT! Thanks Lil Devil!

[+mtn-man]

Not everyone uses one kind of web browser.

I think this would be a great feature for all cachers.

The site over time has added some of these enhancements into the site. A prime example is shown on the page I linked in fact.

 

I've asked for it before, and an answer was, well didn't you see a checkmark next to the cache name on the previous page? But the way I got to the cache page was not through a search so NO there was no page where a checkmark could be shown, except for the completely logical request of this OP on the cache page itself.

Click the link near the maps for all nearby caches. Bingo, for now at least.

 

I also think another, exactly similar request, would be for travel bug pages to show that you have 'grabbed', 'retrieved' or 'discovered' that bug, and not force you to have to page through 20 or more pages of logs on that bug. And of course, why doesn't a list of bugs, such as all the Alien geocoins owned by cacherxyz, not have a checkmark for those that you have logged? Same code that's used on a cache search page, right?

 

travel bugs and geocoin web pages get the short end of the stick when it comes to feature requests (usually) on groundspeak. Perhaps part of the popularity behind PathTags,

Open a separate topic, since this request is off topic. You must have some financial investment in pathtags since you mention them every chance you get, even posting sometimes off topic to mention them (like you did here). In this particular topic you capitalized them but conspicuously chose not to capitalize Groundspeak, a company name, and even deliberately using the color function to make sure that it isn't capitalized since the forum software automatically makes the company name capitalized (note that the quoting of your post makes the "g" black). The second "t" is not capitalized in pathtags, by the way. Of course, answering my question is also off topic. A curiosity.

[+Cache O'Plenty]

There are several pages within the GeoCaching site that would benefit from the Found Checkmark. I've suggested the "DNF" page (the "My Geocaching Logs (Filtered by Log Type)" off of your My Account page) so you could easily tell if you've "cleared" a DNF. Also, your "Watchlist" and some Bookmark lists. In fact, unless a search or list is, by definition, a "Found List", then all pages should show the "Found Checkmark".

 

A separate idea (and probably worthy of it's own topic) would be a filter option on search pages of other cacher's lists (found and owned) that would show those caches NOT found and those FOUND by the logged-on user.

Edited October 25, 2008 by Cache O'Plenty

[+FireRef]

I asked for this a couple of years back, and there appears to be a decent amount of support for this simple software change from a number of people... except Groundspeak. Maybe if we make some noise this time, it will get considered.

 

Or put on the back-burner, like the return of the archived caches to the Google Maps...

[+trainlove]

I also think another, exactly similar request, would be for travel bug pages to show that you have 'grabbed', 'retrieved' or 'discovered' that bug, and not force you to have to page through 20 or more pages of logs on that bug. And of course, why doesn't a list of bugs, such as all the Alien geocoins owned by cacherxyz, not have a checkmark for those that you have logged? Same code that's used on a cache search page, right?

Open a separate topic, since this request is off topic. You must have some financial investment in pathtags since you mention them every chance you get, even posting sometimes off topic to mention them (like you did here). In this particular topic you capitalized them but conspicuously chose not to capitalize Groundspeak, a company name, and even deliberately using the color function to make sure that it isn't capitalized since the forum software automatically makes the company name capitalized (note that the quoting of your post makes the "g" black). The second "t" is not capitalized in pathtags, by the way. Of course, answering my question is also off topic. A curiosity.

 

Off topic?

Same source code to implement this second and completely not different request so I think I now see why travel bug and geocoin pages do get the short end of the stick.

Why do we have to exactly spell out that if a change of type x is done for caches, then the same change should be done for travel bugs? Can't the programmers see the logical outcome of their changes? Are they really so cache centric that they don't know that travel bugs also exist on the site?

[+markandsandy]

Why do we have to exactly spell out that if a change of type x is done for caches, then the same change should be done for travel bugs? Can't the programmers see the logical outcome of their changes?

In a previous lifetime I was a Software Test Engineer. Unfortunately, many programmers get so focused on the problem as it was described to them, that they do not look beyond it to see where else it should have been applied. Can get very frustrating.

[+Cache O'Plenty]

Why do we have to exactly spell out that if a change of type x is done for caches, then the same change should be done for travel bugs? Can't the programmers see the logical outcome of their changes?

In a previous lifetime I was a Software Test Engineer. Unfortunately, many programmers get so focused on the problem as it was described to them, that they do not look beyond it to see where else it should have been applied. Can get very frustrating.

And this is why major applications end up patchworked over time. Has always been a problem unless there is some formal way to send all changes through a Systems Configuration board of some sort.