migrating Preferences class into stand-alone version #1209
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #1104
Changes
Preferencesclass into two classes:app.utils.Preferencesandapp.Preferencesapp.utils.Preferencesclass is the stand-alone version making the loading and saving of preferences independentapp.Preferencesdepends onapp.utils.Preferencesfor the main functionalties (loading, saving, getting a value) but also adds otherappdependent functionalties (fonts, language, ...)PreferencesExceptiondefault.txtis now via JAR resource systemTodo
Baseclass, which forces you to explicitly set the location when usingapp.utils.Preferences. We can decouple it fromBaseclass making it independt ofappmodule