Hi,

I have updated the route finding tools considerably, updating the UI and
replacing the old route finder with my extended version.  It behaves like
the route creator, except whenever you add a new route point, it automatically
finds a route to that new point.  You can switch between adding route points
with the normal route creator tool, and with the route finding tool.

If you guys like it, can it be merged into the main branch?  (I'm not sure how
to do this, the wiki just tells me to have a public fork.)

It can be found here:

    https://github.com/yourealwaysbe/viking-extended-route-finder

Best,

Matt




On Sat, Jan 11, 2014 at 11:07:37pm +0000, Matthew Hague wrote:
> 
> Hi,
> 
> I've had a go at implementing an "extended" route finding tool for Viking.
> I'm sending this mail to 
> 
>     1) see what you think of the tool, whether i'm trampling over any work in
>     progress, and whether it would be suitable to add to Viking proper, and
> 
>     2) get some code review, since i just dived into a large project and
>     hacked around until it worked...
> 
> The idea is that it is a more direct version of the "refine route" option.
> The interface more or less behaves like the "create route" tool.  On the first
> click the user is asked for the name of the route to be created; then, route
> points are added each time the user clicks (with the UI showing route points
> and connecting lines).  The twist is that each time the user adds a route
> point, the default routing web engine is queried to find a route between the
> last point of the track and the new point to be added.  The user presses
> "escape" to finish the planning, or "backspace" or right-clicks to undo the
> last search (and skip back to the penultimate manually entered route point).
> 
> The implementation is available here
> 
>     https://github.com/yourealwaysbe/viking-extended-route-finder
> 
> as a fork of the main git repository.  At the moment i'm just using the same
> button icon as the route finder.
> 
> As part of the implementation i also fixed
> 
>     vik_track_cut_back_to_double_point
> 
> in viktrack.c, since it was casting trackpoints to co-ordinates rather than
> extracting the coord field of the trackpoints.
> 
> Let me know what you think.
> 
> Best,
> 
> Matt
> 

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/

Reply via email to