plasma-framework/templates/qml-plasmoid
2019-01-19 16:09:29 +01:00
..
package SVN_SILENT made messages (.desktop file) - always resolve ours 2018-10-15 05:39:14 +02:00
CMakeLists.txt Remove explicit use of ECM_KDE_MODULE_DIR, part of ECM_MODULE_PATH 2019-01-19 16:09:29 +01:00
Messages.sh Templates: consistent naming, fix translation catalog names & more 2018-05-21 14:08:04 +02:00
qml-plasmoid.kdevtemplate SVN_SILENT made messages (.desktop file) - always resolve ours 2018-11-20 05:36:28 +01:00
qml-plasmoid.png add a couple of plasmoid templates for kapptemplate/kdevelop 2015-11-30 15:02:43 +01:00
README Templates: consistent naming, fix translation catalog names & more 2018-05-21 14:08:04 +02:00

Plasma Applet Template
----------------------

-- Namespace adaption --

Each Plasma plugin has a unique identifier, which is also used to find related
resources (like the translation catalogs).
To avoid naming collisions, Plasma plugins use a reverse domain name notation
for that identifier:

* org.kde.plasma.* - plugins coming from Plasma modules
* org.kde.*        - plugins coming from other software from KDE
* $(my.domain).*   - plugins of your 3rd-party

The generated code uses the "org.kde.plasma" namespace for the plugin identifier.
As this namespace is reserved for use by plugins part of Plasma modules, you will
need to adapt this namespace if you are writing a plugin which is not intended to
end up in the Plasma modules.


-- Build instructions --

cd /where/your/applet/is/generated
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=MYPREFIX .. 
make 
make install

(MYPREFIX is where you install your Plasma setup, replace it accordingly)

Restart plasma to load the applet 
(in a terminal type: 
kquitapp plasmashell 
and then
plasmashell)

or view it with 
plasmoidviewer -a YourAppletName

-- Tutorials and resources --
The explanation of the template
https://techbase.kde.org/Development/Tutorials/Plasma5/QML2/GettingStarted

Plasma QML API explained
https://techbase.kde.org/Development/Tutorials/Plasma2/QML2/API