We (dassIT GmbH) are currently evaluating the possibilities of KDE4 Desktop Environment, for a customer with around 2000 clients. This clients are currently running on KDE3 . This installations are based on centralized profiles.

+

<div class="level2">

<div class="level2">

*<div class="li">Version of KDE: 4.2.4</div>

*<div class="li">Version of KDE: 4.2.4</div>

Line 105:

Line 108:

**<div class="li">a default user in the headquarter uses following KDE configurations: will follow&nbsp;!</div>

**<div class="li">a default user in the headquarter uses following KDE configurations: will follow&nbsp;!</div>

This page shall give you an breath overview, over the main variables which can be set in the plasma-appletsrc. They might be helpful for centralized configurations like Kiosk. The normal users DOES NOT need them in their daily business.

I will now just shortly cover the main variables which can be found in the configuration file.

With this variable we tell the plasmoid at which place we can find it in the panel, it is set through the X-position, y-position. The following last 2 variables are the height and width for the icon, so that plasma can rescale it

immutability

default value is 1. Setting it to 2 disables the possibilities to configure it (configuring includes moving and deleting).

plugin

Defining the type of plugin which should be integrated into the panel, eg. the launcher (KDE4 standard launcher), simplelauncher (KDE3 like launcher)

We (dassIT GmbH) are currently evaluating the possibilities of KDE4 Desktop Environment, for a customer with around 2000 clients. This clients are currently running on KDE3 . This installations are based on centralized profiles.

a default user in the headquarter uses following KDE configurations: will follow !

component

Aim of Test

Changes

Expected Behaviour

Observed Behaviour

Result

panel: resizing

the desktop must stay usable after changing the screen resolution

users uses krandrtray: 800×600 → 1024×768

panel should adapt to new screen resolution

The panel does not adapt itself directly to the new resolution. Initially, it stays at the configured size, but if more applications are opened (plugin=tasks), the panel gets broader. But the panel stays at the left side of the screen. An auto positioning like „center“ would help

(+)

users uses krandrtray to resize screen resolution back to 800×600

panel should adapt to new screen resolution

The panel adapts itself without any problem to a smaller size of the panel. This works also in case there were many windows open. The panel will than decrease automatically

+

panel: moving the panel

the user should be able, to move its panel to different positions

location variable must not be locked with $i. Simply moving the panel by hand

The ordering of the panel icons should stay in the same order und they should not overlap

Moving the panel works without any damage on the panel (damage in this case means complete destruction or at least it becomes unusable)

+

panel: Lock panel for user

We want to be able, to modify the central panel configuration later on. Therefore it is required, that the applet IDs don't change. Therefore we disallow the user to add plasmoids or to move an applet in the panel

We expected that the user can not add a new plasmoid and that the user can not unlock the panel

Indeed the user was not able to add a new plasmoid to the panel and it was not possible as well to unlock the panel. But still, on right-click, the option „unlock panel“ is visible (but without function). Please make it invisible

(+)

Quicklauncher (locked)

There shall be 2 quicklaunchers one for the system configuration and one for the users. The one for the system shall be fixed.

Indeed the user is not able to add/remove any icon which is saved afterwards, but during the normal session the user is able to modify it. After restarting Plasma the Quicklauncher resets to it configured icon set. But we would like to have that the user do not even have the possibilty to click on such a button to add or remove

(-)

Quicklauncher: centrally adding icons

The administrator should be able to add new icons later on

I add a new icon for the firefox into the definition of different files in the configuration of the applet.

The place where I add the new icon in the row of files, is also the place where it is later on shown in the launchbar. So it shall be very easy for the admin to add a new icon.

The quicklauchner behaves as expected, it adds the new icon exactly at the place where I added it in the plasma-appletsrc.

+

Quicklauncher: users taskbar

The user shall have the possibility to add/remove icons from its own quicklauncher