On Fri, Jan 10, 2014 at 05:55:06PM -0000, Sebastien Bacher wrote:
> Hum, I'm not sure I like the idea to make AS the default configuration
> source.
>
> Binding a property to a gsettings key is a 1 liner with gsettings-qt and
> it's quite light on resources, using AS seems quite heavier in code and
> less error proof to me (I trust less the AS service than dconf I guess).
>
> That said that's just personnal feeling, but I think it's a topic worth
> discussing before deciding on a direction.
>
> Michael, do you have an opinion on that? Should we maybe move that
> discussion to a list ?
Then there should be a library. Having to maintain synchronisations
everywhere is pretty bad IMO. It seems pretty obviously the right way to
go to me, but if you want to have a discussion then feel free.
On Fri, Jan 10, 2014 at 05:55:06PM -0000, Sebastien Bacher wrote:
> Hum, I'm not sure I like the idea to make AS the default configuration
> source.
>
> Binding a property to a gsettings key is a 1 liner with gsettings-qt and
> it's quite light on resources, using AS seems quite heavier in code and
> less error proof to me (I trust less the AS service than dconf I guess).
>
> That said that's just personnal feeling, but I think it's a topic worth
> discussing before deciding on a direction.
>
> Michael, do you have an opinion on that? Should we maybe move that
> discussion to a list ?
Then there should be a library. Having to maintain synchronisations
everywhere is pretty bad IMO. It seems pretty obviously the right way to
go to me, but if you want to have a discussion then feel free.
--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]