Abstract away GSettings #186
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a preparation step for ubuntu-flutter-community#183 i.e. migrating from GSettings 0.1 to 0.2. GSettings 0.1 and 0.2 are vastly different because the FFI-based 0.1 is synchronous, whereas the D-Bus-based 0.2 is asynchronous. Furthermore, 0.1 has separate getters for different primitive types, whereas 0.2 has only one getter that returns a DBusValue. In order to make the migration from GSettings 0.1 to 0.2 easier, hide GSettings instances from the models and use nullable setting values to eliminate the assumption that setting values are immediately available.
|
Tyvm! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a preparation step for #183 i.e. migrating from GSettings 0.1
to 0.2.
GSettings 0.1 and 0.2 are vastly different because the FFI-based 0.1 is
synchronous, whereas the D-Bus-based 0.2 is asynchronous. Furthermore,
0.1 has separate getters for different primitive types, whereas 0.2 has
only one getter that returns a DBusValue.
In order to make the migration from GSettings 0.1 to 0.2 easier, hide
GSettings instances from the models and use nullable setting values to
eliminate the assumption that setting values are immediately available.