Difference between revisions of "KF5"

Jump to: navigation, search
(Undo revision 90513 by Colomar (talk))
m (Update links)
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
== Presentation ==
 
== Presentation ==
KDE Frameworks is a framework of libraries built on the top of [http://qt.io Qt]. The libraries are divided in 3 Tiers that define the chain of dependencies.  
+
KDE Frameworks is a framework of libraries built on the top of [https://www.qt.io Qt]. The libraries are divided in four 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 | Ki18n]] library, if you need an archive tool, use [[/KArchive | KArchive]].
+
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 [https://api.kde.org/frameworks/ki18n/html/index.html KI18n] library, if you need an archive tool, use [https://api.kde.org/frameworks/karchive/html/index.html KArchive].
  
 
== 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 [https://api.kde.org/frameworks/ api.kde.org].
  
 
== Examples ==
 
== Examples ==

Revision as of 16:33, 8 January 2017

Presentation

KDE Frameworks is a framework of libraries built on the top of Qt. The libraries are divided in four 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 api.kde.org.

Examples

Getting help

  1. Double-check the api
  2. Try to debug your application [with LINK to how to debug (on community?)]
  3. ask for help on #kde-devel or <mailinglist>
  4. Open a bug on <>

Content is available under Creative Commons License SA 4.0 unless otherwise noted.