f293888be6
We are in a strange cycle when we have a visual parent. In order to obtain our position, we need to know our size. Our size depends on the borders visible. The borders visible depend on the size. When we do not have a visual parent this is not a problem as we do not have a position where we are supposed to be. In order to solve this cycle, when we have a visual parent, we typically assume we have all borders, call popupPosition, move to that position and then use that new position to figure out the borders, get the new size (incase any borders have changed) and move again. This double moving is not good. With that patch, we still do the same but we avoid moving twice.
Plasma Framework
The plasma framework provides the foundations that can be used to build a primary user interface, from graphical to logical components.
Introduction
The plasma framework provides the following:
- A C++ library: libplasma
- Script engines
- QML components
libplasma
This C++ library provides:
- rendering of SVG themes
- loading of files from a certain filesystem structure: packages
- data access through data engines
- loading of the plugin structure of the workspace: containments and applets
See @ref libplasma.
Script engines
Provides support to create applets or containments in various scripting languages.
QML components
org.kde.plasma.core
Bindings for libplasma functionality, such as DataEngine and FrameSvg, see @ref core.
org.kde.plasma.components
Graphical components for common items such as buttons, lineedits, tabbars and so on. Compatible subset of the MeeGo components used on the N9, see @ref plasmacomponents.
org.kde.plasma.extras
Extra graphical components that extend org.kde.plasma.components but are not in the standard api, see @ref plasmaextracomponents.