Hello, > I agree that this would add some redundancy in the definitions of the > key strings, but what I would ultimately want to avoid is to have > '#ifdef GSETTINGS' scattered throughout the client code. Where would > the choice of *definition* for CONF_KEY_ONE be made, if you want to go > with the scheme you are proposing? What would happen tomorrow when a > third backend is proposed, with a different naming scheme? Ok, I'm convinced. You will find in attachment a patch that comes in complement of the previous one and separate the keys implementation into 2 files: nmv-gsettings-keys-defs.cc and nmv-gconf-keys-defs.cc. Also, I noticed an critical bug in my first patch. A patch that will fix it will come soon. Fabien Parent
Attachment:
0002-Move-configuration-keys-implementation-into-one-file.patch
Description: Binary data