Re: [cp-patches] RFC: GConf preference api backend

2006-06-20 Thread Mario Torre
Il giorno lun, 19/06/2006 alle 07.50 -0600, Tom Tromey ha scritto: 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

Re: [cp-patches] RFC: GConf preference api backend

2006-06-20 Thread Michael Koch
On Tue, Jun 20, 2006 at 08:29:04PM +0200, Mario Torre wrote: Using a root of /apps/java makes it clear we are storing java things there, if Sun implements a GConf based backend (or if someone likes my standalone plugin :) they likely will use this name (apps is standard for application in

Re: [cp-patches] RFC: GConf preference api backend

2006-06-20 Thread Mario Torre
Il giorno mar, 20/06/2006 alle 20.46 +0200, Michael Koch ha scritto: We normally avoid the term java as its a registered trademark. We normally prefer the term classpath in our community. Yes, I know, this is one reason why I agree to change the name, my only concern is about compatibility.

Re: [cp-patches] RFC: GConf preference api backend

2006-06-19 Thread Tom Tromey
Tom == Thomas Fitzsimmons [EMAIL PROTECTED] writes: Tom Thanks for this contribution! (FWIW, I wouldn't object if you wanted Tom to make this the default backend now). I think it should only be the default if the peers are enabled. Tom

Re: [cp-patches] RFC: GConf preference api backend

2006-06-19 Thread Tom Tromey
Mario == Mario Torre [EMAIL PROTECTED] 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

Re: [cp-patches] RFC: GConf preference api backend

2006-06-18 Thread Mark Wielaard
Hi Michael, On Sat, 2006-06-17 at 18:07 +0200, Michael Koch wrote: As Mario has no CVS access yet I commited this for him. If you commit something for someone else you MUST make sure that it compiles cleanly, even with --enable-Werror and --enable-regen-headers The following fixes the build:

Re: [cp-patches] RFC: GConf preference api backend

2006-06-18 Thread Michael Koch
On Sun, Jun 18, 2006 at 11:15:26AM +0200, Mark Wielaard wrote: Hi Michael, On Sat, 2006-06-17 at 18:07 +0200, Michael Koch wrote: As Mario has no CVS access yet I commited this for him. If you commit something for someone else you MUST make sure that it compiles cleanly, even with

Re: [cp-patches] RFC: GConf preference api backend

2006-06-18 Thread Mark Wielaard
On Sun, 2006-06-18 at 11:23 +0200, Michael Koch wrote: On Sun, Jun 18, 2006 at 11:15:26AM +0200, Mark Wielaard wrote: On Sat, 2006-06-17 at 18:07 +0200, Michael Koch wrote: As Mario has no CVS access yet I commited this for him. If you commit something for someone else you MUST make

Re: [cp-patches] RFC: GConf preference api backend

2006-06-17 Thread Michael Koch
On Fri, Jun 16, 2006 at 01:56:13PM -0400, Thomas Fitzsimmons wrote: Thanks for this contribution! (FWIW, I wouldn't object if you wanted to make this the default backend now). Please commit, As Mario has no CVS access yet I commited this for him. Cheers, Michael --

[cp-patches] RFC: GConf preference api backend

2006-06-16 Thread Mario Torre
Hi! All the paperwork is signed, so this can be committed as is (if accepted). Fixed from the last (not committed) release is the fact that I'm currently turning the native implementation to reuse libraries in Classpath, most notably, now the native peer uses jcl.h. The idea is to integrate the

Re: [cp-patches] RFC: GConf preference api backend

2006-06-16 Thread Thomas Fitzsimmons
Mario Torre wrote: Hi! All the paperwork is signed, so this can be committed as is (if accepted). Fixed from the last (not committed) release is the fact that I'm currently turning the native implementation to reuse libraries in Classpath, most notably, now the native peer uses jcl.h. The idea