Development/Architecture/KDE4/KParts: Difference between revisions
Neverendingo (talk | contribs) (add translate tags) |
Neverendingo (talk | contribs) (Marked this version for translation) |
||
| Line 1: | Line 1: | ||
<languages /> | <languages /> | ||
<translate>'''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.</translate> | <translate><!--T:1--> | ||
'''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.</translate> | |||
<translate>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.</translate> | <translate><!--T:2--> | ||
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.</translate> | |||
===<translate>Further reading</translate>=== | ===<translate><!--T:3--> | ||
* <translate>[[Special:myLanguage/Development/Tutorials/Using_KParts|Techbase Tutorial: "Using KParts"]]</translate> | Further reading</translate>=== | ||
* <translate>[http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/index.html KParts API Reference]</translate> | * <translate><!--T:4--> | ||
* <translate>[http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/classKParts_1_1Part.html KParts Class Reference]</translate> | [[Special:myLanguage/Development/Tutorials/Using_KParts|Techbase Tutorial: "Using KParts"]]</translate> | ||
* <translate>[http://www-106.ibm.com/developerworks/library/l-kparts/ Coding with KParts] (from IBM)</translate> | * <translate><!--T:5--> | ||
[http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/index.html KParts API Reference]</translate> | |||
* <translate><!--T:6--> | |||
[http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/classKParts_1_1Part.html KParts Class Reference]</translate> | |||
* <translate><!--T:7--> | |||
[http://www-106.ibm.com/developerworks/library/l-kparts/ Coding with KParts] (from IBM)</translate> | |||
<translate>[[Category:KDE4]]</translate> | <translate><!--T:8--> | ||
[[Category:KDE4]]</translate> | |||
Revision as of 00:45, 4 January 2013
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.