Configuration API

[Waldo Bastian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed April 28 2004 09:32, George wrote:
> Basically it's all in the backends.  I bet writing some glue code to be
> able to use one set of backends would be most useful here.  It would not
> tie anyone to any specific API (people are already tied) either.

You can name it backend glue or API, but in the end it's still a common API. 
And yes, I expect both GNOME and KDE to wrap such common API into a platform 
native API. The common API will be the bottle neck because if the common API 
doesn't provide certain functionality, the platform native API will not be 
able to deliver it either.

I think ACAP is a good candidate to look at for inspiration for such common 
API and then see how well that would fit with the requirements of GConf, 
KConfig and others.

Cheers,
Waldo
- -- 
bastian at kde.org |  ...  Watch this space  ...  | bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAj5a7N4pvrENfboIRAm0gAKCd1JZefHPWQrUbK8wz6hMHOB4RVQCgnuUm
S4WonjxZufm00tgD8dvjBtQ=
=RvsI
-----END PGP SIGNATURE-----