[Github-comments] [geany/geany] Start porting to GSettings (#1257)

[elextr]

As discussed on IRC, I agree that the settings system could do with an improvement.  

But I have concerns about the implementation being able to meet the goals of the overarching [project](https://github.com/geany/geany/projects).  If the implementation provides no improvement why do it? (though I might agree that removing custom hand rolled stash is sufficient improvement in itself :)

The areas I see as issues are:

1. Direct binding will not be possible for settings overridden by things like projects and filetypes unless GSettings can handle it itself.  Is this possible?  If not then asynchronous change handling code needs to be provided for those settings, probably just MMOP, but I would like to see that its possible and how complex it is before we commit to the implementation.

2. The current implementation doesn't handle the `-c` option AFAICT, did I miss something?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/1257#issuecomment-251861491
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20161005/5724019f/attachment.html>