Go to file
Marco Martin c8844799eb don't lose the final position on showEvent
if there is an animation running and a showEvent happens, set the position to the supposed endValue before killing the animation

BUG:331981
2014-03-25 16:24:20 +01:00
autotests Fix headers management in plasma-framework 2014-03-17 16:28:24 +01:00
desktoptheme proper push of the breeze theme 2014-03-25 11:56:12 +01:00
examples SVN_SILENT made messages (.desktop file) 2014-03-23 04:47:33 +00:00
src don't lose the final position on showEvent 2014-03-25 16:24:20 +01:00
tests SVN_SILENT made messages (.desktop file) 2014-03-23 04:47:33 +00:00
tools kdebug porting script: enable the useful bits 2014-03-25 02:27:38 +01:00
.reviewboardrc Add reviewboardrc file 2013-08-16 21:58:50 +01:00
CMakeLists.txt Fix headers management in plasma-framework 2014-03-17 16:28:24 +01:00
config-compiler.h.cmake enable build of plasma subdir 2013-01-30 14:53:30 +01:00
config-prefix.h.cmake enable build of plasma subdir 2013-01-30 14:53:30 +01: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
CTestConfig.cmake enable build of plasma subdir 2013-01-30 14:53:30 +01:00
CTestCustom.cmake enable build of plasma subdir 2013-01-30 14:53:30 +01:00
FindPlasma.cmake Try a bit saner setup of the cmake foo 2013-05-03 03:17:26 +02:00
KF5PlasmaConfig.cmake.in Add KF5 prefix to plasma framework 2013-12-11 21:40:54 +01:00
KF5PlasmaMacros.cmake Add KF5 prefix to plasma framework 2013-12-11 21:40:54 +01:00
Mainpage.dox Remove last traces of org.kde.locale 2013-12-19 17:56:12 +05:30
plasma-framework.yaml Add README.md and yaml files 2013-12-20 20:11:24 +01:00
README.md some description 2014-02-10 11:20:50 +01: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 is made by a library component and a runtime component:

  • libplasma: this is a library for the business logic, it manages: ** rendering of SVG themes ** loading of files from a certain filesystem structure: packages ** data access: dataengines ** loading of the plugin structure of the workspace: containments and applets

  • QML script engine: given the data provided by an Applet or a Containment, it maps to loading of an actual QML representation of it

  • QML components: sets of QML components to provide a widget set, and to access to libplasma components, such as SVG themes and dataengines.

  • Runtime environment: the plasma-shell executable. The runtime that will load the actual workspace, it's completely controlled by QML, by itself doesn't have any UI.