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

> This sounds nice to have. But techically KConfig relies on a backend
> and nothing speaks against storing these informations too in the backend.
>
> Kiosk _is_ based on kconfig, so this is either a contra point or no
> argument at all.

Is there some docs on Kconfig somewhere? *looks in CVS*

> Haem, stored where then? in /tmp ? That's at least the only other place my
> user can write to.

I could have my config on a NFS server 1, and my home dir on NFS server 2.

> Which you have to find too, no? What makes a file browser different to
> a registry browser?

Some understanding of the structure of the configuration data, as opposed to 
just having the raw data. Thanks,

David

- -- 
It's not that engineers are boring people, we just get excited about boring 
things.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/OesUfC4dKZ8TgzIRAnDlAJ0aqDFUaeR2xYeBXlGJq73QtLBpHgCbBlOP
ANyHJ3Sim65AEoBMZzg/69E=
=qv5r
-----END PGP SIGNATURE-----

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<