Difference between revisions of "Development/Architecture/KDE4/KParts"

Jump to: navigation, search
(KParts provide flexibility)
(Further reading)
Line 5: Line 5:
  
 
===Further reading===
 
===Further reading===
 +
* [[Development/Tutorials/Using_KParts|Techbase Tutorial: "Using KParts"]]
 
* [http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/index.html KParts API Reference]
 
* [http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/index.html KParts API Reference]
 
* [http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/classKParts_1_1Part.html KParts Class Reference]
 
* [http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/classKParts_1_1Part.html KParts Class Reference]

Revision as of 18:48, 25 April 2010


Development/Architecture/KDE4/KParts

KParts is the name of the component framework for KDE. An individual component is called a KPart. As an example, Konsole is available as a KPart and is used in applications like Konqueror and Kate. Good examples about how KParts can be used are Konqueror, which (among other things) uses the KWord part to display documents, KMPlayer part to play multimedia, and Kontact, which embeds kdepim applications under one roof.

KParts also provide flexibility in your software selection. For example, the KHTML part which is by default used by Konqueror for HTML rendering can very easily be exchanged by a Webkit KPart.

Further reading


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal