[nemo-qml-plugin-configuration] Add a ConfigurationGroup type.

[adenexter]

This provides a convenient API for getting and setting multiple
properties under a common key path.

Properties declared in a ConfigurationGroup are populated with values from the store, and values subsequently assigned to the the property are written back to the store. Groups can also be nested to access hierarchical structures.

ConfigurationGroup {
path: "/path/to/my/settings"
property int myIntegerProperty: 5
property string myStringProperty: "hello world"

ConfigurationGroup {
    path: "nested"
    property real myNestedProperty: 0.3
}

}

[rburchell]

We most likely don't want to do this. In the longer term, migrating away from gconf would be a good thing. dconf provides similar benefits (notification of changes etc) with a much, much better read performance, which is why I was careful to remove gconf-specific behavior from MGConfItem to allow us to switch the backend mostly seamlessly to UI code later on.

If you can figure out a way to hide this in MGConfItem (or somewhere near it, so the switching is easier) and make sure that we can do it with dconf, then I'd be happy to see it in. The API is useful.

[adenexter]

Do you really think porting a second package is going to be more of a maintenance burden than splitting the implementation between two packages?

I guess I could add an MGConfGroup type to mlite though and extend that from the plugin. The concept and implementation are just as applicable to C++ types and it'd be a good way to remove a lot of boiler plate from types like the silica theme object.

[adenexter]

The implementation has moved to mlite nemomobile/mlite#4

This now just provides qml plugin registration.

[adenexter]

The G's have changed to D's and the mlite dependency is now nemomobile/mlite#12

[tanty]

LGTM