Bug 89502 - make kicker lockdown more flexible
Summary: make kicker lockdown more flexible
Status: ASSIGNED
Alias: None
Product: kiosk
Classification: Plasma
Component: kiosktool (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: geiseri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-14 17:43 UTC by Waldo Bastian
Modified: 2009-03-02 04:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Waldo Bastian 2004-09-14 17:43:39 UTC
Version:            (using KDE KDE 3.3.0)
Installed from:    Compiled From Sources
OS:                Linux

We would like to run KDE in mode with special restrictions, e.g.
the customer shouldn't be able to run programs that can be found on
the system by KDE walking through the applnk-path. Therefore the
starter applet is removed from the front-panel (kicker) and
replaced by a special profile-dependant menu,
that provides only applications the user has to work with.

That means that every possibility to run other programs must be switched off by the kiosk system. Therefore we locked down the
mouse-menues and the whole kicker by setting the kickerrc
immutable, as we didn`t find a mechanism to reduce only the
context menu (removing "add .."). Now we have a frozen kicker
that cannot be resized.

Is it possible to make the kiosk restrictions more flexible at this
point ?
Comment 1 Waldo Bastian 2004-11-03 16:53:42 UTC
A similar request for more flexibility:

Make it so that buttons & applets defined at system level can not be removed but that the user can still add additional items himself
Comment 2 geiseri 2009-03-02 04:06:22 UTC
In KDE 4.x there is no more kicker.  That being said we will need to add better integration for the plasma panel in kiosktool.