This task is for documenting the outcome of the mailing list discussion here: https://mail.kdab.com/pipermail/kphotoalbum/2020-April/006574.html
Settings in kphotoalbumrc
Settings that need changing
- Thumbnails (= thumbnail size) → See T12934
- Untagged Tag → Make this a property of the tag: implemented by 9a2898f550382c80067b7a8046b0ed1f0df1018e
- Privacy settings (hide images) → Move this into index.xml (either as 1:1 copy or as property of a tag)
Settings that are not ideal currently
This is a rough list of settings that are currently not in the best config section.
- General/albumCategory → only used for KIPI; removed by fd548130a17458d79de689c1e371c4de4de9e9aa
- General/useExifRotate
- General/useExifComments
- General/stripExifComments
- General/commentsToStrip
- General/ignoreFileExtension
- General/skipSymlinks
- General/skipRawIfOtherMatches
- General/compressBackup
- General/backupCount
- General/trust TimeStamps
- General/excludeDirectories
- General/untaggedImagesTagVisible -> this is a user preference
- FileVersionDetection/load optimization settings → Really storage specific and has nothing to to with file version detection. Possibly make this database-specific
- General/useCompressedIndexXml → This should probably not be a setting at all. The UI should just show the current state and allow the user to convert to (un)compressed format. The setting can be kept as a way to set the default value for new databases.
- FileVersionDetection → Make this datbase-specific.
Possible solutions
Just one thought regarding per-database configuration:
IIRC KConfig supports overlaying of options from different locations (usually distro-defaults, sysadmin-defaults, user-configuration).
Maybe a good approach would be to leverage that feature and have per-database configuration as an additional overlay based on the database location?