Its not a clear feature request, but a suggestion for re-thinking some things which are now based on old concepts. I know there have been different requests about for example making the tracks into categories, just like the points, what I would strongly support, as when you import say 100 tracks there is absolutely no way to delete them, except to try to figure out which one was imported, one by one. The way it's done with points is the proper way to go in my opinion.
But for this whishlist, I just want to mention, that the whole database part is extremely segmented now, and is really really difficult to oversee once you really start using Locus. At the moment, all these functions behave in a slightly different way:
- database - tracks
- database - points
- maps - map elements
- temporary elements
- MyMaps export (why is it not called import???)
- categories for track
- categories for points
- startup phase for loading some elements (like in the database)
- startup phase for loosing others (like in maps - elements)
All these things are actually connected to what elements are visible in the screen, but they are scattered in a million places and all behave a bit differently.
What I'd like to ask is to make a clear new idea / design / architecture for all the database elements. I think as a general idea there should be a clean screen, giving us all the options we ever do with elements, and would consist of a clean design with only 3 tabs:
1. Points - with categories
2. Track - with categories
3. External elements
-> here goes all elements, what are not static in the database but are from datasources
A. from files / directories, like elements now
B. from MyMaps
C. from any other online or virtual data source
The points and tracks would have the same tree-like structure, with folder level and element level selection. All selection would be just a simple tick-box! No more change category, select all, change category, deselect all.
The temporary elements could be just one category for points and tracks.
The external elements would remember the state on startup. For example you'd have a folder on your SD card called: points, caches, tracks, etc. When you make a checkbox to a specific folder or file, Locus would load it up on startup. It might require some caching and looking at file size / file date change, but it's perfectly possible / not very complicated.
MyMaps elements would also load on startup, if there is network connection. If not they would just be using a cached version.
Exporting would work by clicking on any data element, or folder. Importing would have a button. The 4 button screen at the database now is very inefficient, import export doesn't need to be there and we need one more click just to do something.
This is my idea about how to make the database part better in Locus. I believe I'm an experienced Locus user and I find Locus to be more and more complicated to use with such a scattered database structure.
Here is my idea about a simplified, folder structured database screen.
