This object is in archive! 

Unify track information and track editing in a single view

joeloc shared this idea 11 years ago
Completed

The separation of track information and track editing causes a lot of useless complexity in Locus UI. Everything would become much clearer and more logical instantly if these two things were simply unified into a single view like the one above. And you could get rid of quite a few buttons and menus as well. There is no more need for separate view & edit stuff.


How does it work? Clicking on a track will instantly take me to the unified track view. The upper fields are instantly editable. I can simply click the name to change it in place. Or click the folder to change it in place. Or click the creation date to change it in place (yes, should be editable as well).


The style button consists of two things. With the checkmark unset, the style button will be disabled and the track will use the groups default style. With the checkmark set, the style button will be availble and open a popup window with all the style settings. No "extended" crap please, put all the style stuff in one nicely done popup. It is *important* that the button reflects the currently chosen style in some way.


The little "map" on top right is a tiny representation of the track. Very useful.


The other fields are not editable, they simply show more track data. Note that stuff is aligned properly and not horribly centered like in locus` madeningly unreadable current track information window.


Following is the altitude profile. It is OK if you give it a fixed height of about 1/3 width. Thats how all altitude profiles in books and on web pages look like. Scaling it to full screen height light current locus does only looks weirdo.


The description text follows last, it is editable again. Note that it can possibly be in html format. Many track portals put a html formatted description there when you download gpxes.


Thats it. No tabs, no multiple windows, no nonsense. Just ONE SINGLE and PRETTY and possibly scrollable view. Scrolling is one of the most natural things on a smartphone and there is nothing wrong at all with it.

Replies (8)

photo
1

The exact same method can be applied to points as well obviously: merge point information and point editing into a single view. Result: another dozen buttons and menus can be removed from Locus overly complex user interface.

photo
0

The Display of Information (Altitude/Speed) is more clear in this draft than in current Locus track screen "information". A yes for this.


But...


If I`m in the field (or not near a computer), I do need the powerful editing features for creating/editing tracks directly in Locus maps. And it`s good to be able to do this in the current solution.


And I need the existing management for displaying/hiding/sorting tracks.


I also appreciate the current graph display of speed/altitude which is aligned to the single recordingpoints.


I think it`s a good idea to think about redesign, but please mind all the features that would be lost at making it "simple".


Locus is powerful and that`s the way I like it.

photo
1

I am not aware of anything being lost. The track editing directly on the map is not affected. The graph display can just stay the same, it simply moves away from its own tab to the "main" track page.

photo
1

PS: I would never even dream of wanting Locus less powerful, what a strange idea :-). On the contrary... I almost never have a "real" computer available. Locus is all I have to work with... even if it`s a thousand tracks with ten thousand points each :/

photo
1

a reply from


http://forum.locusmap.eu/index.php?to...


The Idea isn`t so bad, but this GUI (Linespace, tables, grafix) is not possible, because older devices have very small displays.


Menion also has to think about non high-end hw user too..


I repeat: the idea is ok... :)

photo
1

Closed tracks filled with color - aka polygons - are in general a bit off-topic during the last months...


There is no need for charts or information of track speed when the track represents a polygon. I might start a discussion about height differences for polygons, but most of the features a standard track uses, are not applicable on polygons.


My wish is to turn off these unused informations in some way. Through settings or config file, don`t mind.


Just saying ;)

photo
2

Excellent idea!

photo
2

SO finally done. About half year ago, such task was done on 'Point screen'. Now finally comes also 'Track screen'. I'm sure you'll like it ;)

Replies have been locked on this page!