Working our way towards 3.13.1
5 views
Skip to first unread message
Steve8x8
Nov 19, 2010, 8:24:34 AM11/19/10
to geotoad
Thanks to helixblue devoting a lot of his time to geotoad for years,
version 3.13.0 has been out for little less than a week now.
As you may have noticed, helixblue is getting more and more busy with
his RL.
Nevertheless, in SVN there's now revision 737 which is supposed to
close some of the open Issues (in particular, those related to
trackables, cache location, and hints). We also have a manual page
now!
Nevertheless, there's still a lot of work to be done.
What's on the list you can check on the Issues page - in particular
we're planning to:
-1- fully support metric units (for search input, and in distance
output)
-2- change the debugging code from "on/off" to multiple logging levels
-3- change the handling of cookies, allowing multiple instances of
geotoad to run in parallel
-4- expand the number of location input formats
-5- create Debian packages
and perhaps a couple more things.
Whether all those enhancements will be in 3.13.[123] isn't clear yet.
But we'll try. Hard.
Here is where you can contribute:
Please test the recent changes, and find the hidden quirks!
There's no ready-made Windows executable, but there's a SVN trunk,
instructions are here:
http://code.google.com/p/geotoad/source/checkout
Please give it a really hard time, testing all special cases you can
imagine. Even the ones you can't ;)
Create GPX files for different searches.
Pass them through gpsbabel (gpsbabel -igpx -ogpx -finput.gpx -
Foutput.gpx) and watch out for warning or error messages.
Put them on your GPSr's SD card, and check cache descriptions,
waypoints, hints, logs, and trackables.
Report everything that doesn't look sane. (It may help to run geotoad
with the -v option, and save stdout and stderr to files. Don't forget
to provide the search details that lead to the problem.)
If you hesitate to make your findings public (here, or under Issues),
or if you're unsure whether you have found a bug or a feature - write
me (stev...@gmail.com).
3.13.1 (and the next versions) will be as good (or bad) as you make
it. Go for the best, now!
Cheers,
Steve
version 3.13.0 has been out for little less than a week now.
As you may have noticed, helixblue is getting more and more busy with
his RL.
Nevertheless, in SVN there's now revision 737 which is supposed to
close some of the open Issues (in particular, those related to
trackables, cache location, and hints). We also have a manual page
now!
Nevertheless, there's still a lot of work to be done.
What's on the list you can check on the Issues page - in particular
we're planning to:
-1- fully support metric units (for search input, and in distance
output)
-2- change the debugging code from "on/off" to multiple logging levels
-3- change the handling of cookies, allowing multiple instances of
geotoad to run in parallel
-4- expand the number of location input formats
-5- create Debian packages
and perhaps a couple more things.
Whether all those enhancements will be in 3.13.[123] isn't clear yet.
But we'll try. Hard.
Here is where you can contribute:
Please test the recent changes, and find the hidden quirks!
There's no ready-made Windows executable, but there's a SVN trunk,
instructions are here:
http://code.google.com/p/geotoad/source/checkout
Please give it a really hard time, testing all special cases you can
imagine. Even the ones you can't ;)
Create GPX files for different searches.
Pass them through gpsbabel (gpsbabel -igpx -ogpx -finput.gpx -
Foutput.gpx) and watch out for warning or error messages.
Put them on your GPSr's SD card, and check cache descriptions,
waypoints, hints, logs, and trackables.
Report everything that doesn't look sane. (It may help to run geotoad
with the -v option, and save stdout and stderr to files. Don't forget
to provide the search details that lead to the problem.)
If you hesitate to make your findings public (here, or under Issues),
or if you're unsure whether you have found a bug or a feature - write
me (stev...@gmail.com).
3.13.1 (and the next versions) will be as good (or bad) as you make
it. Go for the best, now!
Cheers,
Steve
Steve8x8
Nov 20, 2010, 11:28:35 AM11/20/10
to geotoad
(You certainly have watched "Short Circuit"? Life is not a
malfunction.)
> Please test the recent changes, and find the hidden quirks!
to have verbose mode on - please use the command line option "-v", or,
when running the TUI, toggle verbosity with the "v" key to "on" before
"s"tarting the search.
It's hard to reproduce an error if the only input is "I did a search
within twenty miles of radius" - please provide the command line (the
TUI will show it when it starts searching) as an absolute minimum!
Please take into account also that we - helixblue and myself - don't
have Premium Member status - if the caches involved are members-only,
without access to the cache description page we might be unable to
reproduce the problem.
In such cases, the last 10--25 lines of debugging output (and, of
course, the Ruby error messages) may be the only clue.
Linux users may use "tee" to write stdout to a file without losing the
opportunity to watch geotoad working.
Here is what I do when testing:
geotoad ....... 2>run.err | tee run.out
If the very last line of output isn't "( o ) Saved to ..." then
something went wrong.
In such a case, please provide
- the command line (without username and password, of course)
- the full contents of the error output
- the last line containing "wid = " from standard output
- the last, say, 20 lines of standard output
The more complete the information, the faster the problem can be
reproduced and worked on.
Thanks for your attention!
Cheers,
Steve
malfunction.)
> Please test the recent changes, and find the hidden quirks!
> Please give it a really hard time, testing all special cases you can
> imagine. Even the ones you can't ;)
> imagine. Even the ones you can't ;)
> Report everything that doesn't look sane. (It may help to run geotoad
> with the -v option, and save stdout and stderr to files. Don't forget
> to provide the search details that lead to the problem.)
Please try to provide as much information as possible. It's essential
> with the -v option, and save stdout and stderr to files. Don't forget
> to provide the search details that lead to the problem.)
to have verbose mode on - please use the command line option "-v", or,
when running the TUI, toggle verbosity with the "v" key to "on" before
"s"tarting the search.
It's hard to reproduce an error if the only input is "I did a search
within twenty miles of radius" - please provide the command line (the
TUI will show it when it starts searching) as an absolute minimum!
Please take into account also that we - helixblue and myself - don't
have Premium Member status - if the caches involved are members-only,
without access to the cache description page we might be unable to
reproduce the problem.
In such cases, the last 10--25 lines of debugging output (and, of
course, the Ruby error messages) may be the only clue.
Linux users may use "tee" to write stdout to a file without losing the
opportunity to watch geotoad working.
Here is what I do when testing:
geotoad ....... 2>run.err | tee run.out
If the very last line of output isn't "( o ) Saved to ..." then
something went wrong.
In such a case, please provide
- the command line (without username and password, of course)
- the full contents of the error output
- the last line containing "wid = " from standard output
- the last, say, 20 lines of standard output
The more complete the information, the faster the problem can be
reproduced and worked on.
Thanks for your attention!
Cheers,
Steve
Steve8x8
Nov 30, 2010, 7:00:38 AM11/30/10
to geotoad
There are rumours that 3.13.1 might be released soon. Well, in 2010,
perhaps. ;)
> > Please test the recent changes, and find the hidden quirks!
> > Please give it a really hard time, testing all special cases you can
> > imagine. Even the ones you can't ;)
> > Report everything that doesn't look sane. (It may help to run geotoad
> > with the -v option, and save stdout and stderr to files. Don't forget
> > to provide the search details that lead to the problem.)
Please extend your tests to /branches/steve8x8 as it contains some
additional stuff which I'm using (and thereby testing) on a regular
basis.
You may, as an alternative, start with the svn trunk, and apply
patches selectively - get them (tarball) from
http://steve8x8.faehrwiese.selfhost.me/my-geotoad/
- remember to use the -p1 option to patch!
New features which *might* be included into 3.13.1 *if* properly
reviewed are:
- short WP names (GC.Wombat97 did some testing yet)
- distances in km, both on the command line and in the TUI
- some support for GCStatistic ("myfindgpx")
For my own purposes, I have decided to use more readable filenames
(reducing the number of underscore characters), and have a more
detailed progress bar. I don't know whether you like them...
> Please try to provide as much information as possible. It's essential
> to have verbose mode on - please use the command line option "-v", or,
> when running the TUI, toggle verbosity with the "v" key to "on" before
> "s"tarting the search.
applied.
Please do not open new issues when your reports fits into an existing
one.
In the end, it's Thomas' choice what to include into the next release.
Give him useful input (and/or me the opportunity to fix stuff):
Both pros and cons are welcome - remember, there'll be a life even
after 3.13.1 ;)
Thanks,
S.
perhaps. ;)
> > Please test the recent changes, and find the hidden quirks!
> > Please give it a really hard time, testing all special cases you can
> > imagine. Even the ones you can't ;)
> > Report everything that doesn't look sane. (It may help to run geotoad
> > with the -v option, and save stdout and stderr to files. Don't forget
> > to provide the search details that lead to the problem.)
additional stuff which I'm using (and thereby testing) on a regular
basis.
You may, as an alternative, start with the svn trunk, and apply
patches selectively - get them (tarball) from
http://steve8x8.faehrwiese.selfhost.me/my-geotoad/
- remember to use the -p1 option to patch!
New features which *might* be included into 3.13.1 *if* properly
reviewed are:
- short WP names (GC.Wombat97 did some testing yet)
- distances in km, both on the command line and in the TUI
- some support for GCStatistic ("myfindgpx")
For my own purposes, I have decided to use more readable filenames
(reducing the number of underscore characters), and have a more
detailed progress bar. I don't know whether you like them...
> Please try to provide as much information as possible. It's essential
> to have verbose mode on - please use the command line option "-v", or,
> when running the TUI, toggle verbosity with the "v" key to "on" before
> "s"tarting the search.
> In such a case, please provide
> - the command line (without username and password, of course)
> - the full contents of the error output
> - the last line containing "wid = " from standard output
> - the last, say, 20 lines of standard output
and of course the SVN revision you're using, and which patches you
> - the command line (without username and password, of course)
> - the full contents of the error output
> - the last line containing "wid = " from standard output
> - the last, say, 20 lines of standard output
applied.
Please do not open new issues when your reports fits into an existing
one.
In the end, it's Thomas' choice what to include into the next release.
Give him useful input (and/or me the opportunity to fix stuff):
Both pros and cons are welcome - remember, there'll be a life even
after 3.13.1 ;)
Thanks,
S.
Steve8x8
Dec 4, 2010, 8:09:12 AM12/4/10
to geotoad
On Nov 30, 1:00 pm, Steve8x8 <steve...@googlemail.com> wrote:
> There are rumours that 3.13.1 might be released soon. Well, in 2010,
> perhaps. ;)
I was wrong.
> There are rumours that 3.13.1 might be released soon. Well, in 2010,
> perhaps. ;)
It's 3.14.1 :)
What the project page http://code.google.com/p/geotoad/ doesn't tell
you:
There's a source .tar.gz next to the .zip - containing exactly the
same stuff.
There's a .deb package. Debian/Ubuntu packaging is still experimental
(but supposed to work).
Please download what fits your needs best, and provide feedback!
Cheers,
S.
Reply all
Reply to author
Forward
0 new messages