[Loadstone] Routes and trips.

Dave Mielke dave at mielke.cc
Tue Oct 9 03:18:36 BST 2007


[quoted lines by Shawn Kirkpatrick on 2007/10/08 at 17:01 -0700]

>They're a list stored in memory. This avoids having to do any lookups using 
>the database engine.

i believe this is a good thing for features such as these. Here are some 
suggestions:

I see a tracked or recorded trip and a user-defined route as being the same 
thing except for how the data is entered. In both cases one wants to end up 
with an ordered list of checkpoints. That's what loadstone already has. To make 
these features work, therefore, I think there are four features which need to 
be added.

First: Regardless of how the data is entered, both features need the currently 
loaded checkpoint list to be editable. This means that there needs to be a way 
to bring up the list of checkpoints, and for each item to have options like 
rename, move (up or down within the list), delete, "go to" (see second feature) 
to select the next point, and "explore" (see fourth feature) to find out what's 
near by. The "explore" function would probably be more useful if it only 
considered unchecked points, i.e. points not on the route.

Second: Regardless of how the data is entered, there needs to be a way to 
activate the currently loaded checkpoint list as a rrute. By default, the next 
checkpoint to go to would be the first one in the list, although the user could 
use the "go to" function (see first feature) to tell loadstone where he 
actually is on the route. Loadstone would only monitor the next checkpoint (the 
selected item) until the user gets there, at which time it'd to an implicit "go 
to" to the next item in the list. It could even warn the user if he's moving 
away from the point.

Third: Defining a route is probably as simple as adding a point to the end of 
the currently loaded checkpoint list whenever it's checked. That's probably 
already the way it's done. A useful enhancement, though, would be the ability 
to check a point while it's being defined. Adding this to the save point 
submenu would be convenient.

Fourth: For recording a trip it needs to be possible to both automatically and 
manually add points. Automatic points clearly need to be added each time the 
user changes direction, but should probably also be added at a regular time 
interval even if the user doesn't change direction. The name for an 
automatically added point should begin with the word "auto", and include the 
time it was added as well as the direction in which the user was moving (the 
new direction if a change). This information, in conjuction with the "explore" 
option (see first feature) will help the user later when he goes through the 
points to give them more meaningful names. A manually added point should have a 
similar default name except that it should begin with "user" rather than 
"auto", but should also allow the user to immediately assign a more meaningful 
name.

That's my initial proposal in order to get some discussion going.

-- 
Dave Mielke           | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: dave at mielke.cc | Canada  K2A 1H7   | if you're concerned about Hell.
http://FamilyRadio.com/                   | http://Mielke.cc/bible/


More information about the Loadstone mailing list