Comment 12 for bug 1035343

Revision history for this message
Joshua Judson Rosen (rozzin) wrote : Re: [Bug 1035343] Re: Feature: Add route planning support to foxtrotgps (Patch included)

"Dr. Tilmann Bubeck" <email address hidden> writes:
>
> Yes, you are right: it is very unclear. When I started hacking on
> tangoGPS, then "set WP" and "unset WP" and also "get route" had no
> function at all. I though about removing them, but let them stay because
> I did not know what they are used for.

In addition to positioning a flag icon, `set WP' causes a targetting-
arrow to be added to the GPS location-indicator (if you have a GPS
attached and the GPS has a fix); so, while the GPS position indicator
will normally show you in which direction you're moving, `set WP'
will cause it to *also* show the direction in which your WP lies.
Useful in navigating toward a destination without having a specific
route planned/plotted.

> However, I would prefer if we put the different things in different
> menus
[...]
> A better alternative may be, to change the "get route" stuff to use "my"
> routepoints. The "get route" dialog would disappear and the "get route"
> menu entry would use all route points which were set by "route planning"
> and send them to "yournavigation.org" (or other servers). The result
> would be displayed like before.
>
> So you could think of a two step route planing:
> (1) set route points and save them to let a vehicle navigation system
> do the route finding. STOP here.
> (2) or CONTINUE and let "yournavigation.org" find a route through
> the points with no further vehicle navigation system.

Oh, *that* is a neat idea!

> But this would be a bigger change. Maybe release often and early in two releases?
> * release 1.2.0: menus changed like the discussion above
> * release 1.2.1: integrate route finding like "alternative" above.
>
> What do you think?

I think that sounds like a good plan.

--
"Don't be afraid to ask (λf.((λx.xx) (λr.f(rr))))."