6cbea20bf9
Summary: preload popups of some applets after init in the background based on a value of X-Plasma-PreloadWeight in the desktop file if present, otherwise some default values based on the applet type (Provides) Save the weight in the config, if an applet is never opened, slowly decrease the weight, when it reaches 0 don't preload it next start, increase every time it gets opened, so at the moment it's quite aggressive about preloading, in order to not do it a lot of plasma startups without touching the applet are needed Applet with a very big weigth will be preloaded immediately, therefore having an impact on the time it will take to have a panel visible and usable, while lesser weigths will preload after a random number of seconds between 2 and 10, so will load in the background after everything is started Test Plan: Plasma starts up correctly, applets load correctly and can be added correctly both those expanded or collapsed. plasmashell appears correctly usable without too big hiccups even while it's loading things in the background some numbers: without preloading, plasma takes around 64 mb of memory after startup when preloading everything about 94, so it's a cost of about 30 mb which is not negligible. don't have precise timing, but if everything gets preloaded immediately, the time to get an usable desktop appears to be at least doubled, while the delayed preloading (except just a couple of applets) doesn't seem to have a big impact on the time needed to get an usable desktop Reviewers: #plasma Subscribers: davidedmundson, broulik, apol, ngraham, plasma-devel, #frameworks Tags: #plasma, #frameworks Differential Revision: https://phabricator.kde.org/D10512 |
||
|---|---|---|
| autotests | ||
| docs | ||
| examples | ||
| src | ||
| templates | ||
| tests | ||
| .arcconfig | ||
| CMakeLists.txt | ||
| COPYING | ||
| COPYING.LIB | ||
| ExtraDesktop.sh | ||
| KF5PlasmaConfig.cmake.in | ||
| KF5PlasmaMacros.cmake | ||
| metainfo.yaml | ||
| README.md | ||
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.