Re: Exposing gconf key names



> Now, this key is "owned" by gnome-vfs (i.e. it is described / defined in
> a schema file that gnome-vfs installs), along with a number of other
> gconf keys. Would it make sense, therefore, for gnome-vfs to expose
> these keys via some constants in a public header file? 

I think that makes sense. Adding a function call which reads the key and
returns it to the app may also be useful, that would allow gnome-vfs to
handle your backward compatibility concern.

Christophe

Attachment: signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]