Development/Architecture/KDE4/KParts: Difference between revisions
m (Development/Architecture/KDE 4 Architecture/KParts moved to Development/Architecture/KDE4/KParts: less redundant path) |
|||
| Line 2: | Line 2: | ||
===Further reading=== | ===Further reading=== | ||
* [http://api.kde.org/ | * [http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/index.html KParts API Reference] | ||
* [http://api.kde.org/cvs-api/kdelibs-apidocs/kparts/html/classKParts_1_1Part.html KParts Class Reference] | * [http://api.kde.org/cvs-api/kdelibs-apidocs/kparts/html/classKParts_1_1Part.html KParts Class Reference] | ||
* [http://www-106.ibm.com/developerworks/library/l-kparts/ Coding with KParts] (from IBM) | * [http://www-106.ibm.com/developerworks/library/l-kparts/ Coding with KParts] (from IBM) | ||
[[Category:KDE4]] | [[Category:KDE4]] | ||
Revision as of 18:06, 19 August 2007
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.