Code Monkey home page Code Monkey logo

Comments (10)

HarelM avatar HarelM commented on June 24, 2024

A few minor corrections:
There's no long click/right click in the app, the menu opens up when you click on a route point while editing.
You can also do a route that overlap itself by clicking next to an exiting route and dragging the added point to the route, you don't have to combine routes.
This is a side note obviously, the discussion here is about how to improve the current short comings of the current approach.

from site.

Tsurha avatar Tsurha commented on June 24, 2024

Thanks for the clarifications.

Option 1 - "always continue"

To elaborate, the behavior is:

  • If while editing the user clicks on a place without a point, a new point is added to the end. This is both if that place is outside the current route (excising behavior) and if that place is on the current route (new behavior).
  • If while editing the user clicks on a place that already has a dot, the menu opens up (excising behavior, see picture). A new scissors tool is not needed (earlier I thought it was needed).
  • Adding points in the middle will be done by dragging the route sideways and dragging it back. This functionality is already supported. but this will dramatically change recorded routes

image

Option 2 - toggle

  1. As discussed, in option 2 toggling between "add points" mode and a new "always continue" mode could be with an icon in the editing icon column. We just did not know how will it look like. If this is chosen, will have to carefully design two A+B icons that explain it. At least a tool tip on it can add wording.
    scissors

Note that with one color for a route, the user will not be able to distinguish between points on the route on one direction from points on the opposite direction. Two colors will be preferable here. If so, it has to be defined more.

from site.

HarelM avatar HarelM commented on June 24, 2024

As explained on the phone, when editing a recorded route (not a planned one) dragging a middle point can change the route dramatically (consider a place that doesn't have a way on the map and was recorded, moving it will completely move the route to a different place).
In that case, there might be a need to be able to cut the recording in a specific place, and for that a middle point is needed.

from site.

Tsurha avatar Tsurha commented on June 24, 2024

I've edited my previous comment per yours, since it is challenging for option 1.

Lets consider option 2 with two different modes. We did not know what could their icons look like. Here is one possibility / idea:

AB

from site.

HarelM avatar HarelM commented on June 24, 2024

Any chance you can update the initial comment and remove the second one
I just feel there's a lot of duplicate info there, and it's hard to understand what is the last proposal in general.

Regarding your last post about an icon, it's easy to understand what it means given this context, and if the images are presented side-by-side, but if you click on the image and it toggles from one state to the other it's harder to really grasp the difference, and without this context it's even harder.
I would recommend, as an interesting experiment, to post the image only and ask in the facebook group what do people think this means.
I'll be surprised if more than 30% will get it right :-).
If we add a button to the top editing menu, a scissors icon that you can toggle on and off (with the green frame) is a lot more intuitive I believe.

from site.

Tsurha avatar Tsurha commented on June 24, 2024

I just created a route back and forth with your idea of points near by, and dragging them to the route. It works well and seems like the whole discussion here is not worth the effort.

from site.

HarelM avatar HarelM commented on June 24, 2024

Interesting turn of events 😀 I'll keep this open nevertheless for now and see how I feel about it. Maybe involve our new UX people too to take this into consideration.

from site.

zstadler avatar zstadler commented on June 24, 2024

Having two modes, a.k.a. the toggle option, is complicating the UX. This is a move in a direction that we've avoided as much as we could. I would not support it for the problem described here.

This leaves us with considering the best UX for the "click" and "click and drag" operations somewhere on the existing route.

IMO, a "click and drag" somewhere on the existing route could only do what it does now: create a new intermediate point at the location where the drag ended and re-route to that point and from it. This should remain also when considering any form of "always add to the end" UX.

If I followed the discussion correctly, there are two options on the table for the "click" (without a drag) operation when performed somewhere on the existing route:

  1. Create a new intermediate point and do not do any re-routing, as is today
  2. Create a new end point and a route to it.

Option 1 is used in the current UX as a preparation step for a few user scenarios, including:

  • Mark a place for splitting a trace into two traces
  • Mark a place to block re-routing when editing a recording

If Option 2 is used, the way to add an intermediate point would be to perform "click and drag" back and forth. Since "click and drag" re-calculates the route, this option will make editing of recordings practically impossible.

Similarly, "click and drag" can also be used to mimic "Option 2" when option 1 is used. As @HarelM suggested: click anywhere near the intended location of the new end point and drag it to the desired location.

Without trying to estimate the importance of the three user scenarios discussed here, Option 1 is supported by two user scenarios (splitting a route and editing a recording) and Option 2 is supported by one (route twice on same segment). The later has a reasonable workaround if Option 1 is used. However, the editing a recording user scenario has no reasonable workaround if Option 2 is used.

Therefor I think Option 1 is the better option to use.

from site.

HarelM avatar HarelM commented on June 24, 2024

It's worth noting that on the go map has similar behavior - click is always adding a point at the end of a route and dragging is to create a middle segment with routing.
It doesn't seems to have an option to open a GPX file though, so the part about cutting a recording is probably not relevant.
https://onthegomap.com/#/create

from site.

github-actions avatar github-actions commented on June 24, 2024

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days

from site.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.