c9e8c4b38c
numerous icon tests expect the actual production plasma theme to be present it won't however be resolved because we disable qstandardpaths' default fallbacks by switching it into testing mode. this ultimately means the test run needs to have XDG_DATA_DIRS in the environment, if it doesn't test data will not be present furthermore QSKIP tests that depend on: - hicolor icon theme to be present - production plasma themes this allows the entire test to pass in less than optimal environments by means of skipping but also gives a reasonable hint as to why tests are skipped in the first place. also moving forward if a test isn't guarded we still have the warning about failure potential allowing someone to quickly figure out why things failed REVIEW: 127764
Plasma Framework
Foundational libraries, components, and tools of the Plasma workspaces
Introduction
The plasma framework provides the following:
- QML components
- A C++ library: libplasma
- Script engines
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.
org.kde.plasma.plasmoid
Attached properties for manipulating the current applet or containment, see @ref libplasmaquick
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.