Go to file
Vishesh Handa f293888be6 Dialog: Avoid adjusting the geometry twice when with visualparent
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.
2014-08-28 18:25:03 +02:00
autotests tests for isValid and hasValidStructure 2014-08-08 14:12:22 +02:00
docs fix plasmapkg2 manpage 2014-05-05 13:16:05 +02:00
examples bind setAssociatedApplicationUrls 2014-08-07 19:34:57 +02:00
src Dialog: Avoid adjusting the geometry twice when with visualparent 2014-08-28 18:25:03 +02:00
tests Dialog Test: Add a test for making the dialog fullscreen 2014-08-28 16:29:00 +02:00
.reviewboardrc Fix .reviewboardrc syntax 2014-06-02 17:39:23 +01:00
CMakeLists.txt Upgrade ECM and KF5 version requirements for 5.1.0 release. 2014-08-02 08:21:59 +00:00
COPYING Add COPYING and COPYING.LIB files 2013-12-23 18:39:10 +00:00
COPYING.LIB Add COPYING and COPYING.LIB files 2013-12-23 18:39:10 +00:00
KF5PlasmaConfig.cmake.in Fix Plasma_INCLUDE_INSTALL_DIR variable in config module 2014-04-26 12:56:34 +01:00
KF5PlasmaMacros.cmake Don't install dummydata folders with plasma_install_package 2014-06-12 16:42:43 +02:00
metainfo.yaml Add metadata about the QMake and CMake packages installed by this framework and remove Links from README.md 2014-08-13 10:56:51 +02:00
README.md Add metadata about the QMake and CMake packages installed by this framework and remove Links from README.md 2014-08-13 10:56:51 +02:00

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.