[go: up one dir, main page]

Jump to content

KDE Frameworks

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Psypherium (talk | contribs) at 09:34, 19 August 2021 (now using wikidata instead of template for latest release version in infobox). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

KDE Frameworks
Original author(s)KDE
Developer(s)KDE
Initial release1 July 2014; 10 years ago (2014-07-01)
Stable release
6.5.0[1] Edit this on Wikidata / 9 August 2024; 3 months ago (9 August 2024)
Repository
Written inC++ (Qt)
Operating systemCross-platform (including "partial" support for Android,[2][3] Windows,[4] macOS and Haiku)
Type
LicenseGNU Lesser General Public License (LGPL)[5]
Websiteapi.kde.org/frameworks/index.html Edit this on Wikidata

KDE Frameworks is a collection of libraries and software frameworks readily available to any Qt-based software stacks or applications on multiple operating systems.[6] Featuring frequently needed functionality solutions like hardware integration, file format support, additional graphical control elements, plotting functions, spell checking the collection serves as technological foundation for KDE Plasma 5 and KDE Applications distributed under the GNU Lesser General Public License (LGPL).[7]

Overview

Current KDE Frameworks are based on Qt 5, which enables a more widespread use of QML, a simpler JavaScript-based declarative programming language, for the design of user interfaces. The graphics rendering engine used by QML allows for more fluid user interfaces across different devices.[8]

Some source code was moved from being part of KDE Frameworks 5 to being part of Qt 5.2 and later.

Since the split of the KDE Software Compilation into KDE Frameworks 5, KDE Plasma 5 and KDE Applications, each sub-project can pick its own development pace. KDE Frameworks are released on a monthly basis[9] and use git.[10][11]

It should be possible to install KDE Frameworks alongside the KDE Platform 4 so apps can use either one.[12]

API and ABI stability

Platform releases are those which begin a series (version number X.0). Only these major releases are allowed to break binary compatibility with the predecessor. Releases in the minor series (X.1, X.2, ...) will guarantee binary portability (API & ABI). This means, for instance, that software that was developed for KDE 3.0 will work on all (future) KDE 3 releases; however, an application developed for KDE 2 is not guaranteed to be able to make use of the KDE 3 libraries. KDE major version numbers mainly follow the Qt release cycle, meaning that KDE SC 4 is based on Qt 4, while KDE 3 was based on Qt 3.

Supported operating systems

The repository of each framework should contain a file named metainfo.yaml.[13] This file documents the maintainer of the framework, the type, the supported operating system and other information. The currently supported platforms are Linux, Microsoft Windows, macOS and Android.

Software architecture

Structure

The Frameworks have a clear dependency structure, divided into "categories" and "tiers". The "categories" refer to runtime dependencies:

  • Functional elements have no runtime dependencies.
  • Integration designates code that may require runtime dependencies for integration depending on what the OS or platform offers.
  • Solutions have mandatory runtime dependencies.

The "Tiers" refer to compile-time dependencies on other Frameworks.

  • Tier 1 Frameworks have no dependencies within Frameworks and only need Qt and other relevant libraries.
  • Tier 2 Frameworks can depend only on Tier 1.
  • Tier 3 Frameworks can depend on other Tier 3 Frameworks as well as Tier 2 and Tier 1.

Components

The KDE Frameworks bundle consists of over 70 packages. These existed as a single large package, called kdelibs, in KDE SC 4. Kdelibs was split into several individual frameworks, some of which are no longer part of KDE but were integrated into Qt 5.2.[14]

KDE Frameworks are grouped in four different tiers according to dependency on other libraries. Tier 1 frameworks only depend on Qt or other system libraries. Tier 2 frameworks can depend on tier 1 libraries, Qt and/or other system libraries and so forth.[15]

Kirigami

Kirigami is a QML application framework[17] developed by Marco Martin[18] that enables developers to write applications that run natively on Android, iOS, Windows, Plasma Mobile and any classic Linux desktop environment without code adjustments.

It is used by various applications, for example Linus Torvalds and Dirk Hohndels scuba diving application Subsurface, the messenger client Banji,[19] the Kaidan messenger,[20] Vvave music player and the KDE software center Discover.

Software packages

Linux distribution use some package management system to package the software they distribute. Debian for example distributes KGlobalAccel under the package name libkf5globalaccel,[21] while Fedora distributes it under the name kf5-kglobalaccel.[22]

Bindings

While being mainly written in C++, there are many bindings for other programming languages available:[23][24]

  • Python
  • Ruby (Korundum, built on top of QtRuby)
  • Perl
  • C# (however, the current framework for binding to C# and other .NET languages has been deprecated, and the replacement only compiles on Windows).[25]

These and other bindings use the following technologies:

Many bindings weren't updated to Qt5 and KF5 or only later in the release cycle.

History

The 5.0 release was preceded by a technology preview, two alpha releases, and three beta releases.[26][27][28]

The source code of KDE Frameworks has been around since KDElibs 1. The first release as KDE Frameworks was with version 5, to account for the fact that the code base was that of KDE Platform version 4 (the only major version of KDE Platform).

The transition from KDE Platform to KDE Frameworks began in August 2013, guided by top KDE technical contributors.[8]

After the initial release of KDE Frameworks 5.0, the developers focused on adding new features to the components in KDE Frameworks 5,[29] an example being better integration of Firefox into KDE.[30]

The major improvement of Frameworks 5 is its modularization. In earlier KDE versions, the libraries were bundled as a single large package. In Frameworks, the libraries were split into individual smaller packages. This facilitates utilization of the libraries by other Qt-based software, since dependencies can be kept at a minimum.[8]

While KDE 4 was based on version 4 of the Qt widget toolkit, Frameworks 5 is based on version 5.

KDE4 transformation

During KDE SC 4, the then so called KDE Platform consisted of all libraries and services needed for KDE Plasma and the applications. Starting with Qt 5, this platform was transformed into a set of modules that is now referred to as KDE Frameworks. These modules include: Solid, Nepomuk, Phonon, etc. and are licensed either under the LGPL, BSD license, MIT License or X11 license.[31]

Adoption

Besides the KDE Software Compilation, there are other adopters such as the desktop environments LXQt, MoonLightDE or Hawaii.

Version 3.0 of Krita, the raster graphics editor of the Calligra Suite, which was released on May 31, 2016, depends on KDE Frameworks 5 and Qt 5.2.

With Kirigami, there is also increased usage by applications such as Amarok, Avogadro, Trojitá or Subsurface.

References

  1. ^ "KDE Ships Frameworks 6.5.0". 9 August 2024. Retrieved 20 August 2024.
  2. ^ "Release of KDE Frameworks 5.24.0". 9 July 2016.
  3. ^ "Android - KDE Community Wiki".
  4. ^ https://api.kde.org/
  5. ^ "First release of KDE Frameworks 5". 2014-07-07.
  6. ^ "The KDE Frameworks". API Documentation.
  7. ^ "KDE Frameworks". Tech Base.
  8. ^ a b c Howard Chan (2013-09-04). "KDE Release Structure Evolves". KDE. Retrieved 2014-02-27.
  9. ^ "Release schedule for KDE Frameworks 5".
  10. ^ "Git workflow for Frameworks".
  11. ^ "KDE Frameworks5 API documentation". Archived from the original on 2014-08-22.
  12. ^ "Coinstallability with KDE Platform 4".
  13. ^ "metainfo.yaml of KConfig".[permanent dead link]
  14. ^ Jos Poortvliet (2013-12-17). "Qt 5.2 - Foundation for KDE Frameworks 5". Dot.kde.org. Retrieved 2014-03-10.
  15. ^ Howard Chan (2013-09-25). "Frameworks 5". Dot.kde.org. Retrieved 2014-03-10.
  16. ^ "KWindowSystem in Frameworks 5". 6 February 2014.
  17. ^ "KDE Kirigami". KDE. Retrieved November 25, 2018.
  18. ^ "Contributors to KDE/Kirigami".
  19. ^ https://youtube.com/watch?v=LjyKtusCy2Y
  20. ^ https://github.com/KaidanIM/Kaidan
  21. ^ "KGlobalAccel in Debian".
  22. ^ "KGlobalAccel in Fedora".[permanent dead link]
  23. ^ "The KDE development platform". Retrieved 2010-11-26.
  24. ^ Development/Languages - KDE TechBase. Techbase.kde.org (2012-07-12). Retrieved on 2013-07-17.
  25. ^ "Qyoto". Retrieved 2015-01-18.
  26. ^ "Frameworks 5 Technology Preview". KDE. 2014-01-07.
  27. ^ "KDE Ships First Alpha of Frameworks 5". KDE. 2014-02-14.
  28. ^ "KDE Ships Second Alpha of Frameworks 5". KDE. 2014-03-03.
  29. ^ "KF5 Update Meeting Minutes 2014-w28". 2014-07-08.
  30. ^ "Firefox + KDE integration: Getting FF to use Dolphin reliably". 2014-07-03.
  31. ^ "KDE Licensing Policy". Retrieved 2010-11-06.