Re: plasma and new shadow mess

Thomas L├╝bking thomas.luebking at gmail.com
Mon Jan 7 14:15:21 GMT 2013


On Montag, 7. Januar 2013 10:51:11 CEST, Aaron J. Seigo wrote:

> it is a library. that does not rely on the desktop (or other) shell. it 
> provides shared functionality for applications in kde-workspace, but without
> a guaranteed API for others (ergo no headers).

=========

$ for name in /usr/bin/*; do if [ ! -z "`ldd "$name" | grep libplasmagenericshell`" ]; then echo "$name"; fi; done

/usr/bin/krunner
/usr/bin/plasma-desktop
/usr/bin/plasma-netbook
/usr/bin/plasma-overlay

---

$ ls libs/plasmagenericshell

BackgroundDialog.ui  backgrounddialog.cpp  mouseplugins.h         plasma-layout-template.desktop  toolbutton.h
CMakeLists.txt       backgrounddialog.h    mousepluginwidget.cpp  plasmagenericshell_export.h     wallpaperpreview.cpp
Messages.sh*         mouseinputbutton.cpp  mousepluginwidget.h    scripting/                      wallpaperpreview.h
MousePlugins.ui      mouseinputbutton.h    panelshadows.cpp       tests/                          widgetsexplorer/
TODO                 mouseplugins.cpp      panelshadows.h         toolbutton.cpp

=========

So it provides panelshadows, a widgetexplorer, a "Click to change how an action is triggered" mouseinputbutton, a wallpaperpreview, a backgrounddialog (seems wallpaper picker) ...

plasma-* are thin wrappers on the libs that effectively form the desktop shell.
If it wasn't, KWin and other stuff was by now "linking" the desktop process (usually in order to use a common theme) anyway, and if the WM links "libplasmagenericshell.so" it is even *semantically* the gnome/unity approach - or i need a new dictionary.

Thomas




More information about the kde-core-devel mailing list