Default folder and filename for exports

[RogerF]

Here is a suggestion to facilitate exports of items like tracks from the logbook.
It could as well be generalised to other exports.

- Trigger: Logbook / Long press on a flight / Share / Export / Tracks (KML,GPX)

- Current behaviour:
=> The top level of the internal memory (or sd cardis shown, depending on the place where FlyIsFun is stored.
=> The filename field is empty (no default proposal).

- Problem:
=> The user needs to navigate to the target folder and then type a filename.
The full sequence has to be repeated for each exported trace.

- Suggestion:
=> Remember the last folder used for an export and use it next time an "Export" (or even Import) is called.
=> Propose a filename by default for tracks, based on the track data:
for a flight starting on 28 August 2018 at 15:17 to fly with the aircraft OOVVH from EBTX to EBLG, the default filename could be: 2018-08-28_1517_OOVVH_EBTX-EBLG
=> The user is able to delete or amend the default filename if he/she is not happy with it.

Thank you in advance for considering this proposal; I think that it would highly speed up the export of a series of tracks.

[kitercuda]

Version 21.30 stores last used directory.

[RogerF]

Tested OK.

Thanks!
Roger

[RogerF]

I come back to my suggestion as it contained actually two suggestions.
The first one (default folder) has been implemented - thanks Petr!

The second one was somehow forgotten and I revive it here:

- Trigger: Logbook / Long press on a flight / Share / Export / Tracks (KML,GPX)

- Current behaviour:
=> The filename field is empty (no default proposal).
=> The user has to type the full filename every time.

- Suggestion:
=> FlyIsFun is smart enough to detect and show many elements in the flights list (logbook).
=> This knowledge could be used to propose a default filename when exporting a track.
=> Propose a filename by default for tracks, based on the track data.

Example:
- date-time of start: 28 August 2018 at 15:17
- aircraft: OOVVH
- Departure airfield: EBTX
- Arrival airfield: EBLG
=> Proposed filename: 2018-08-28_1517_OOVVH_EBTX-EBLG

Of course, the user should keep the possibility to modify the filename if needed.
In case some fields (e.g. departure, arrival) are unknown, they could simply be omitted:
- Example: 2018-08-28_1517_OOVVH
In case some fields (e.g. aircraft name) would contain illegal characters, they should simply be skipped or replaced by spaces.

Thank you in advance, Petr, for considering this proposal.
It would highly facilitate the export, especially when exporting a series of tracks.

[Tonio]

Hi Roger

Concerning the logbook export name, don't you think that the easiest / generic name could be
"Logbook export from date to date"

[RogerF]

Your proposal makes sense to export the whole list of flights headers (CSV).

My proposal concerned the export of a single flight track, but the same naming scheme could be used for exporting a whole selection of flight "in one go".
In this case, the gpx or kml export should create one file per flight: having several tracks in one file is not practical for a post-ops analysis.

[kitercuda]

Next upgrade...