public Class PreferencesMigrations

The legacy key smartFileAnnotations toggled a "smart visibility" mode. Mode was adapted for all tabs in EntryEditor as content driven visibility.

In 5.0 the format of column names have changed. That made newer versions of JabRef preferences incompatible with earlier versions of JabRef. As some complains came up, we decided to change the variable names and to clear the variable contents if they are unreadable, so former versions of JabRef would automatically create preferences they can deal with.

In version 6.0 the formatting of the CleanUps preferences changed. Instead of using several keys that have have a variable name a single preference key is introduced containing just the active cleanup jobs. Also instead of a combined field for the field formatters and the enabled status of all of them, they are split for easier parsing.

Changes

The former preferences default of columns was a simple list of strings ("author;title;year;..."). Since 5.0 the preferences store the type of the column too, so that the formerly hardwired columns like the graphic groups column or the other icon columns can be reordered in the main table and behave like any other field column ("groups;linked_id;field:author;special:readstatus;extrafile:pdf;...").

Simple strings are by default parsed as a FieldColumn, so there is nothing to do there, but the formerly hard wired columns need to be added.

In 5.1 variable names in JabRefPreferences have changed to offer backward compatibility with pre 5.0 releases Pre 5.1: columnNames, columnWidths, columnSortTypes, columnSortOrder Since 5.1: mainTableColumnNames, mainTableColumnWidths, mainTableColumnSortTypes, mainTableColumnSortOrder

Up to and including v6.0-alpha.6, custom entry editor tabs were stored in two parallel numbered series (customTabName_0/customTabFields_0, ...). Since #16598 they are stored as one JSON object, {"tab name": ["field pattern",...], ...}. The old keys are kept in case an old version of JabRef is used with these preferences; they are only read when the new key does not exist yet.

Migrate Import File Name and Directory name Patterns from versions <=4.0 to new BracketedPatterns

Updates unchanged key bindings in snapshots persisted before macOS-specific defaults were introduced.

upgrade the old theme css names of the theme to the new theme properties Theme names were changed in #15573

The old keys are deleted after reading them, so the migration runs at most once -- migrations run on every startup, and re-applying the old value each time would overwrite whatever the user selected in the new UI in the meantime.