Improve sorting functionality of Track folders / Tracks

[nazar-kutz]

Summary of Changes and Future Considerations

1. Unified Interfaces

Implemented shared interfaces TracksGroup and ComparableTracksGroup for:

• TrackTab, TracksFolder, SmartFolder.

Added a getId() method to TracksGroup, returning:

• TrackFolder: Relative path (e.g., "A/B/C" for "tracks/A/B/C"). Relative path doesn't include global tracks root folder ("tracks" in Adnroid, "GPX" in iOS).
• SmartFolder: Prefixed name, e.g., for "test" folder name, id is "SMART_FOLDER___test". The prefixe "SMART_FOLDERS___" is ​​used to determine whether a given id belongs to a smart folder or not.
• TrackTab: Replaces previously implemented method getTypeName() on getId() to return folder/smart folder ID or type name (ON_MAP, ALL, FOLDERS).

2. Enhanced TrackFolder Functionality

• getRootFolder() returns root folder ("tracks" for Android, "GPX" for iOS).
  Updated getDirName() to support an extended name format (useExtendedName parameter):
• TrackFolder: Returns relative path.
• SmartFolder: Unaffected by parameter.
• TrackTab: Includes parent folder if not root.

3. Optimized PreselectedTabParams

Replaced name with id field and removed redundant code for parsing SmartFolder IDs.

4. Refactored TrackTabsHelper

Created SelectTrackTabsHelper subclass for logic specific to SelectTrackTabsFragment.

5. TrackFolder ID Methodology

Replaced usage of folder name as ID with the getId() method that will return a relative path to the folder from the root folder ("tracks" for Android, "GPX" for "iOS"). Also fixed relative path retrieving to always exclude root folder name. It meens that previously for root folder getRelativePath() returned a string "tracks". Now it returns an empty string "". It was implemented because of different names of root tracks forlder for Android and iOS for implementing consistency between these platforms.

6. TrackSortModesCollection Wrapper

Implemented a new class TrackSortModesCollection. It centralized sort mode management:

• Supports both relative path (new key) and folder name (legacy key). This is required to ensure the ability to read the sort mode using the new key, even if the settings are stored with the old key (e.g., after importing settings from previous app versions).
• Auto-upgrades keys via askUpgradeCachedKeys during runtime. We try to update the keys each time we request TrackSortModesCollection from OsmandSettings. To ensure the keys are updated correctly, access to all TrackFolders is required. This means that at the time of the update, all track folders must be loaded using TrackFolderLoaderTask. The key upgrade to the new version occurs only once per application session. This is done to avoid redundant operations, as all cached keys are updated during the first run, and new keys are immediately added in the form of a relative path.
• Dynamically updates keys on folder rename/delete.

7. Improved TrackTab sorting functionality

• To implement sorting by distance and duration we calculate and cache TrackFolderAnalysis. Currently without recalculating on tracks changes, such as moving track to another folder or remove it.
• Implemented getSortedTrackTabs() using TracksComparator for TrackTab-s.
• Sorting adapts to UI context:
  • Horizontal tab menu (no parent folder).
  • Dialog window (includes parent folder).

8. Sorting Logic depends on context

Sorting is applied differently depending on the context:

• My Places → Tracks screen
  • Regular folders and smart folders are displayed as a single, combined list.
  • They are sorted according to the mode selected for the root folder "Tracks."
• Configure Map → Tracks (tabs and bottom sheet)
  • All smart folders are displayed regardless of whether they contain tracks.
  • Regular folders appear only if they contain one or more tracks (excluding subfolders content).
  • Tabs display only the folder name.
  • In the bottom sheet, the folder name is accompanied by its parent folder name if it is not the root folder ("tracks").
  • Smart folders and regular folders are separated into two distinct lists, each sorted independently but using the same sorting mode (as set for the root "tracks" folder).
  • The list starts with global types (ON_MAP and ALL), followed by sorted smart folders and regular folders.

To account for tab type during sorting, the ComparableTracksGroup class introduces the getDefaultOrder() method:

• This method applies only to TrackTab and returns the index of the tab type via TrackTabType.ordinal().
• It allows different types to be divided into separate lists and sorted independently during the creation of the overall list.

Suggestions for iOS

Unifying sort modes handling across Android and iOS

To ensure better compatibility between Android and iOS, consider implementing functionality similar to TrackSortModesCollection. While it doesn’t have to be an identical bundle, the following should be ensured:

• Ability to fetch sort modes from settings using old keys (folder name) if the settings were imported from a previous app version.
• Update keys from folder name to folder path as implemented in method askUpgradeKeysWithSync.
  This will help maintain consistency across Android and iOS implementations, improving support for shared features.

Updating the getRelativePath method for TrackFolder

The getRelativePath method in TrackFolder has been modified to no longer return "GPX" as the relative path for the root folder. This change ensures key consistency between Android and iOS.
However, on iOS, it is necessary to verify whether this update disrupts existing logic. Other settings might have used the path as a key, and if so, they should be adjusted accordingly.

Replacing getRelativePath with getId

It is recommended to replace all calls to getRelativePath() with getId() for TrackFolder. Although both methods currently return the same value, using getId explicitly makes the code clearer and better reflects its purpose.