0d3a814e20
we were creating new packagestructures on each package creation and never deleting them, causing a pretty big leak. now keep a single instance of the structures, with prototype packages. members are static for binary compatibility. i would go for max one bic change in this library that's when and if this library will be made pubic. Patch by Aaron Seigo
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.
Links
- Wiki: http://community.kde.org/Plasma#Plasma_Workspaces_2
- Mailing list: https://mail.kde.org/mailman/listinfo/plasma-devel
- IRC channel: #plasma on Freenode
- Git repository: https://projects.kde.org/projects/playground/libs/plasma-framework/repository