Wishlist: Request for all logs instead of just 10

[GoogleCodeExporter]

What steps will reproduce the problem?

1.Run a search
2.geotoad.rb --delimiter='|' --distanceMax=5 --output='removed' 
--queryType=location --titleKeyword=train 'postcode removed' -M
3.

What is the expected output? What do you see instead?

I'd like to see all logs for each cache (or at least be able to provide a 
maximum).  At the moment I only get a maximum of 10 logs for a cache.

What version of the product are you using? On what operating system?

3.18.1

Please provide any additional information below.

Original issue reported on code.google.com by hieg...@gmail.com on 12 Nov 2013 at 7:38

[GoogleCodeExporter]

Hm, nice request. (I remember people asking for _less_ logs in the past.)
Due to the inner logic of GeoToad, this seems impossible currently - as all 
information is retrieved from the printable pages, which - to my knowledge - 
are limited to 10 log entries. (There had been rumours, and even requests in GS 
forums, to have more log entries in the print version, but they apparently 
never made it public.)

If you find a way to use a value different from 5 or 10, in the 
"cdpf.aspx?guid=...&lc=nn" URL, I'd be happy to use it. For now there's little 
hope :(

Also, I'd like to suggest to make this an Enhancement, instead of a Defect. 
What do you think?

- S

Original comment by Steve8x8 on 13 Nov 2013 at 8:13

[GoogleCodeExporter]

Yes I overlooked how to make this an enhancement.  Thanks for the explanation.

Original comment by hieg...@gmail.com on 13 Nov 2013 at 7:59

[GoogleCodeExporter]

A few more words about this issue. 
GeoToad, long before I joined the project, had been designed to use the 
"printable pages". Which was a very good idea given the modification rate of 
GroundSpeak's design for the "cache details" page - the parser would break 
every three weeks on average. Note that the "dynamic" display of log entries on 
the cache details page had been invented long thereafter, and the logbook 
concept is also rather young compared to GeoToad which had been created in 
early 2003 (and had a predecessor named geocrunch in 2002).
Adapting GeoToad to the recent changes (and structures) might be a nice project 
for someone with too much time at their hands, but would also push the 
frequency of necessary updates. To be honest, I still prefer to *use* GeoToad - 
to prepare my geocaching excursions - instead of ironing out wrinkles every 
week which I didn't make myself. But volunteers are welcome - it absolutely 
can't harm if someone with fresh ideas looks over that old code.

In short - with the given, inherited, framework and the still valid limitation 
by GS (one would fall back to 5 log entries if the "lc" value isn't supported), 
this request will stay on the wishlist.

(Changing the issue type to "Enhancement".)

- S

Original comment by Steve8x8 on 14 Nov 2013 at 1:10

• Changed title: Wishlist: Request for all logs instead of just 10
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I would be interested as well to have it as a parameter for the supported 
values (0, 5 or 10).

Original comment by geocachi...@gmail.com on 23 Nov 2013 at 4:31

[GoogleCodeExporter]

#4: Obviously it's not easy to make everyone happy - 0, 5, 10, or perhaps 100 
log entries... (please suggest an option letter...)

As a short-term measure to set the log count to 0: as GeoToad now also searches 
your own config tree for templates, it should be simple to "clone" the existing 
templates, and cut out the <%*log%> stuff. (I guess that's another thing that 
needs better documentation... any takers?)

Original comment by Steve8x8 on 24 Nov 2013 at 7:56

[GoogleCodeExporter]

I was mentioning those values because that's the one offered by GC, with the lc 
parameter (you may use the same option letter?).

Thanks for the short-term solution for zero log.

Original comment by geocachi...@gmail.com on 1 Dec 2013 at 7:47

[GoogleCodeExporter]

As a starting point, I renamed the "-l" option to "-w" (the long option will 
remain "--waypointLength") in the trunk.
There's a patch to limit the output of logs ("-l 2" will result in two logs, 
plus the "info" entry in GPX; "-l 0" will completely suppress log output, even 
the "info" one) in my local space, but it won't make it into 3.19.1.
Default is "-l 10". Should there ever be access to "print pages" with more than 
10 logs I'll change the code to fetch as many as possible.

Original comment by Steve8x8 on 16 Dec 2013 at 12:36

• Changed state: Started

[GoogleCodeExporter]

Thanks, Merry Christmas.

Original comment by geocachi...@gmail.com on 21 Dec 2013 at 9:13

[GoogleCodeExporter]

Option -l can now be used to limit the number of log entries (for whatever 
reason). There's still no known trick to extend the count beyond 10 - if you 
find out how, please teach me.

Original comment by Steve8x8 on 27 Dec 2013 at 1:37

• Changed state: FixAvail

[GoogleCodeExporter]

The -l option is in the 3.19.2 release, so one half of the issue is "Fixed".
Unless there's a way to get a "printable page" with more than 10 logs, the 
other half of the issue is "WontFix". Closing for now.

Original comment by Steve8x8 on 6 Jan 2014 at 1:48

• Changed state: WontFix