Download/Upload custom configuration sets

[ce-bo]

Feature request

Description

As an auditor, I want download and upload my custom configuration files, so that I can share them between other devices, browsers and people. Also, I want to use them as backup.

Acceptance criteria

• The download button is removed if experimental features are enabled
• A download button is shown left to the "plus" button within the Custom Configs Panel.
  • On hover a tooltip is shown for downloading the configs. to be discussed.
• The download button is only active if at least one configuration exists that is related to one of the loaded maps.
• The downloaded file contains all configuration data that is related to the currently loaded maps.
• For a single map the filename should be composed with the map name and the current date (e.g. map-example_YYYYmmdd_hh:mm.cc.config.json)
• On saving a new configuration the total storage size is checked.
  • Some facts regarding the localStorage:
    • It does not exist a limit for the total localStorage size that applies to all browsers.
    • Usually 2MB - 10MB are available (5MB seems to be very common but Opera has supported only 2MB some time ago).
    • The localStorage size (e.g. 5MB) is assigned per origin.
    • localStorage characters are stored in UTF-16.
    • It seems that the localStorage per origin is occupied by a 3KB default overhead.
  • If it exceeds 768KB trigger a warning for the user that contains the request to store old configurations to make space for new ones. Purge old configurations files on acceptance. At least 50% of the configuration files should be freed. Per default all configuration files that has not been accessed within the last 6 months
• It is possible to upload .cc.json files and .cc.config.json files toghether.
  • the .cc.config.json files will be stored in the local storage.
• On upload existing configuration files should be matched. Duplications should be prevented.
  • Different configuration files with the same name (mode and assigned maps) should be renamed and both should be kept.
    • t.b.d. how to rename them?

Assumptions & Exclusions

• Downloading configs is useful to share them with other people, to save them for other devices and browsers and to use them as backup. This should be shown in the tooltip.

Development notes (optional Task Breakdown)

• Store when a configuration was last applicable to be able to purge possibly outdated/unneeded config files.

Open Questions

@BridgeAR Should we reset the creation timestamp of a CustomConfig during the import, so that a new "Download & Purge" request will not delete them again?