(→Printing) |
(put the bit about kdeglobals vs individual apps in the general intro) |
||
| Line 1: | Line 1: | ||
This article contains a listing of known keys that can be used with Kiosk and what they do. How to actually use these keys and other capabilities of Kiosk such as URL restrictions, creating assigning profiles, etc. is covered in the [[../Introduction|Introduction to Kiosk]] article. | This article contains a listing of known keys that can be used with Kiosk and what they do. How to actually use these keys and other capabilities of Kiosk such as URL restrictions, creating assigning profiles, etc. is covered in the [[../Introduction|Introduction to Kiosk]] article. | ||
| + | |||
| + | Which configuration file to put these entries in depends on whether you wish to make them global to all applications or specific to one application. To make the restrictions valid for all applications, put them in {{path|kdeglobals}}. To enable a restriction for a specific applications place them in the application-specific configuration, e.g. {{path|konqererorrc}} for Konqueror. | ||
== Application Action Restrictions == | == Application Action Restrictions == | ||
| Line 52: | Line 54: | ||
KDE applications can take advantage of many types of resources such as configuration data, caches, plugin registries, etc. These are loaded from both system-wide as well as from per-user locations on disk. It is possible to restrict use of the per-user resources directories, preventing users from adding to or altering existing shared resources. | KDE applications can take advantage of many types of resources such as configuration data, caches, plugin registries, etc. These are loaded from both system-wide as well as from per-user locations on disk. It is possible to restrict use of the per-user resources directories, preventing users from adding to or altering existing shared resources. | ||
| − | This is accomplished by creating a section like this in a configuration file | + | This is accomplished by creating a section like this in a configuration file: |
<code ini> | <code ini> | ||
This article contains a listing of known keys that can be used with Kiosk and what they do. How to actually use these keys and other capabilities of Kiosk such as URL restrictions, creating assigning profiles, etc. is covered in the Introduction to Kiosk article.
Which configuration file to put these entries in depends on whether you wish to make them global to all applications or specific to one application. To make the restrictions valid for all applications, put them in kdeglobals. To enable a restriction for a specific applications place them in the application-specific configuration, e.g. konqererorrc for Konqueror.
There are several keys that restrict various aspects of the KDE print dialog and printing system. To use them, create a configuration section like this:
[KDE Resource Restrictions][$i]
print/<resource key>=false
Note how each of the printing keys start with print/<tt> in the configuration file.
KDE applications can take advantage of many types of resources such as configuration data, caches, plugin registries, etc. These are loaded from both system-wide as well as from per-user locations on disk. It is possible to restrict use of the per-user resources directories, preventing users from adding to or altering existing shared resources.
This is accomplished by creating a section like this in a configuration file:
[KDE Resource Restrictions]
<resource key>=false
The following resources can be used as keys and controlled in this manner:
| Key | Directory | Provides |
|---|---|---|
| all | n/a | All resources listed in this table |
| autostart | share/autostart | Apps to start on login |
| data | share/apps | Application data |
| data_<appname> | share/apps | Application data for the application named <appname> |
| html | share/doc/HTML | HTML files |
| icon | share/icon | Icons |
| config | share/config | Application configurations |
| pixmap | share/pixmaps | Images |
| xdgdata-apps | share/applications | Application .desktop files |
| sound | share/sounds | Sound files |
| locale | share/locale | Localization data |
| services | share/services | Protocols, plugins, kparts, control panels, etc. registry |
| servicetypes | share/servicetypes | Plugin definitions, referenced in services registry entries |
| mime | share/mimelnk | Mimetype definitions |
| wallpaper | share/wallpapers | Desktop wallpaper images |
| templates | share/templates | Document templates |
| exe | bin | Executable files |
| lib | lib | Libraries |
In kdeglobals in the [KDE Action Restrictions] group:
In kscreensaverrc:
[ScreenSaver]
AutoLogout=true
AutoLogoutTimeout=600
The timeout is the time in seconds that the user must be idle for before the logout process is automatically started. Be careful with this capability as it can lead to data loss if the user has unsaved files open.
These keys apply to various capabilities associated with a desktop session and are not application specific. To use them, create a section in kdeglobals that looks like this:
[KDE Action Restrictions]
<key>=false
KDE TechBase 