KDE-Forum.org

KDE Kiosk has a mailinglist https://mail.kde.org/mailman/listinfo/kde-kiosk

I am sure you will find any help you need there.

Cheers,
_

Quoted

Original von gloin

Quoted

Original von anda_skoa

KDE Kiosk has a mailinglist https://mail.kde.org/mailman/listinfo/kde-kiosk

I am sure you will find any help you need there.

Cheers,
_

Thanks for your reply. But so far, no joy there, which is why I posted here =]

Ah, too bad. Even the Kiosk mode maintainer is subscribed there.

Anyway, I'll give it a shot, but it is just pointers, haven't tried anything like that before.

1) Start Konqueror through a shellscript in KDE's Autostart folder.
The script has to contain a loop, e.g a while loop with always true condition, and in this loop you start konqueror with a profile you want.
If konqueror quits, the loop takes another iteration and start konqueror again.

2) I think Kicker's content is configured in kickerrc.
You can create a configuration you like and put it in the global KDE directory for configs (usually KDEPREFIX/share/config).
Then you disable changability of the file by putting [$i] into an extra line at the very beginning of the file, see this
http://www.kde.org/areas/sysadmin/config_file.php#lock_down
for details.

3) I am not sure if this has any bad side effects, but you could try to remove the file.protocol file from KDEPREFIX/share/services

4) no idea here

5) Not sure how this is handled, but perhaps removing the programs of each MIME type in Control Center->KDE components->file associations works.

6) no idea either, might work to have a fixed (see above) configuration file for kprinter

7) that should be doable with locking down konqueror's config file konquerorrc

KDEPREFIX/share/apps/konqueror/konqueror.rc describes which actions are present in which order in the menus/toolbars.
Remove the ones you don't need.

Cheers,
_

Quoted

Original von gloin

Some of this stuff I'm handling by setting permissions... for example, chmod 644 /home/path/to/kickerrc sets the properties to immutable.

Might not work for all programs, e.g. they could crash if not able to write their files.
Marking the file as immutable also has the advantage, that new settings in the higher level file are automatically used.

Quoted

My other question is this: can I create a kdeglobals file in a given user's home dir rather than creating a systemwide file?

Hmm, good question.
Try to create .kdeglobals in the user's home dir or kdeglobals in .kde/share/config

Quoted

I'm looking for fine-grained user-level control here - maybe not as important for the instant case, but down the road I will need to create profiles for students who log in versus staff, versus admins, etc.

I think you can use KDE Dir trees for that
http://www.kde.org/areas/sysadmin/fsh.php#dir_location

Quoted

Looking at the action restrictions, it sure would be nice if there were a way to wildcard them - I'm looking at a hundred lines or so of code to set all the restrictions =[

Short of creating your own version of konqueror.rc including only the actions you want, I think it is only possible to remove the ones you don't want from the original file.

Cheers,
_