[cp-patches] RFC: GConf preference api backend
tromey at redhat.com
Mon Jun 19 13:50:13 UTC 2006
>>>>> "Mario" == Mario Torre <neugens at limasoftware.net> writes:
Mario> The backend works, but there are few problems when using some kinds of
Mario> keys, most notably, keys with white spaces and other "special"
Mario> characters (ie. "<" and ">").
Mario> This problem is gconf related, and there is at least one bug entry in
Mario> the gnome bugzilla:
I'm curious about this.
What is the failure mode that an application will see if it tries to
use a bad key? Is there a failure mode we'll see when GConf is
My concern is that if we end up having to work around this on the
Classpath side, then we'll have to implement some kind of name munging
scheme -- breaking existing classpath-created GConf databases. I
suppose we could add a version number to the internally-added path
It might be handy to have a 'classpath tracking PR' that depends on
all the gnome bugs that affect classpath.
Mario> user root: /apps/java
Maybe should be /apps/classpath?
More information about the Classpath-patches