KDE Frameworks: Difference between revisions
No edit summary |
(Added link to Kirigami HIG) |
||
Line 6: | Line 6: | ||
== API == | == API == | ||
You can find the API documentation of the Frameworks on: [http://api.kde.org/frameworks-api/frameworks5-apidocs/ apidox] | You can find the API documentation of the Frameworks on: [http://api.kde.org/frameworks-api/frameworks5-apidocs/ apidox] | ||
== Kirigami HIG == | |||
If you want to get the most out of the Kirigami Components framework for mobile and convergent user interfaces, we suggest getting familiar with the [[/KirigamiHIG | Kirigami Human Interface Guidelines]] before using them. | |||
== Examples == | == Examples == |
Revision as of 16:01, 13 April 2016
Presentation
KDE Frameworks is a framework of libraries built on the top of Qt. The libraries are divided in 3 Tiers that define the chain of dependencies.
You don't need to use all the libraries: they are divided in a way that allow you to choose what you really need. For instance if you need to localize your application, use the Ki18n library, if you need an archive tool, use KArchive.
API
You can find the API documentation of the Frameworks on: apidox
Kirigami HIG
If you want to get the most out of the Kirigami Components framework for mobile and convergent user interfaces, we suggest getting familiar with the Kirigami Human Interface Guidelines before using them.
Examples
Getting help
- Double-check the api
- Try to debug your application [with LINK to how to debug (on community?)]
- ask for help on #kde-devel or <mailinglist>
- Open a bug on <>