[Panel-devel] KDE/kdebase/workspace

[Sebastian Sauer]

Aaron J. Seigo wrote:
>> Because when we have several applets on desktop we want to put them in a
>> specific position. We won't want to move it by accident.
>> and if we want to lock them we must have a menu for it.
> 
> 
> if "we" is "the system administrator" then no, that's what kiosk is for.
> if "we" is the person using the desktop, then that is what the hover
> interface will be for.
> 
> please talk to us on panel-devel before adding these kinds of features =)
> thanks..
> 
>> > the patch is also broken in numerous ways, primarily surrounding kiosk
>> > and immutability.
>>
>> Why ?
>> Menu entry is put after test if immutability and kiosk option.
> 
> slotLockApplet is a protected slot. any subclass can then call it and
> thereby circumvent kiosk. even worse, setLockApplet is a public method.
> 
> now that i understand what you were going for, i'll fix the code up.
> thanks..

Would it be an idea to provide access to the KMenu in 
DesktopView::contextMenuEvent somehow to be able to extend the contextmenu 
with applet related things? Probably just allow an applet to define an own 
i18n("%1 ...",applet->name()) submenu or allow to merge menus?