Ideas and Migration steps

OUTDATED

The different data saved by c:geo should first of all be assigned to those two categories as follows:

1. Data which needs to be accessed by the user outside of c:geo:

• Database backup
• All file exports (field notes, GPX)

2. Data which can be considered internally as the user typically does not need to access/modifiy it:

• Cached cache data
• Database

This would allow to use the following strategy afterwards:

For 1. the target directory should either be requested when performing the action or be predefined but changeable in our settings.

For 2. we should go towards the standard android implementation to store it either internally or on the real external SD card. The database - as it is needed to run c:geo - should always stay on the internal storage to avoid problems.

Possible migration steps:

1. Remove the option to store the database in getExternalStorageDirectory()/.cgeo/ and (if the setting was previously active) relocate the database back to getFilesDir ()
2. Implement user definable directories (in the settings) for field note export and database backup.
3. Prompt the user if he wants the /.cgeo/ to be moved to internal or external storage and move it to the selected storage.
4. Implement a setting for the desired storage (see 3.) so that the user can move the location if required. Changing the setting should move the existing files.