-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 03 December 2001 10:17 pm, Christopher Dawkins wrote:
It is easy because it is all controlled by text files in areas (on our system) such as /usr/share/applnk and /usr/share/config and ~/.kde/share. These text files are easily edited by hand or by scripts, which might be run by cron, and easily protected against user modification if the users don't have root access.
It is difficult because you need to know the structure of the applnk and config and rc files and the interactions between them, and you then need to know how to write the appropriate scripts.
I agree. ;) That's what my app would hopefully address. It turns out that another KDE developer has done quite a lot of work on looking at this. You can find his ideas at http://webcvs.kde.org/kdelibs/kdecore in the file README.kiosk. Hopefully I will be able to share some ideas with him. - -- Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP key: http://chrishowells.co.uk/pgp.txt KDE: http://www.koffice.org, http://edu.kde.org, http://usability.kde.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8DI5PF8Iu1zN5WiwRAtM8AJwNWQuBH2cQhkDnsj7bH4kAnb8nwQCdE/QU IyOw9OFDJTeGnz4Dg1kvC8s= =FBRs -----END PGP SIGNATURE-----