[go: up one dir, main page]
Jump to content

KDE Frameworks: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
m maintenance tag
AnomieBOT (talk | contribs)
Bots
6,509,201 edits
m Dating maintenance tags: {{Only primary sources}}
 
Line 1: Line 1:
{{short description|Collection of libraries and software frameworks for the Qt framework}}
{{short description|Collection of libraries and software frameworks for the Qt framework}}
{{Only primary sources}}
{{Only primary sources|date=July 2024}}
{{Infobox software
{{Infobox software
| name = KDE Frameworks
| name = KDE Frameworks

Latest revision as of 14:17, 10 July 2024

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, and spell checking, the collection serves as the technological foundation for KDE Plasma and KDE Gear. It is distributed under the GNU Lesser General Public License (LGPL).[7]

Overview

[edit]

KDE Frameworks is based on Qt, 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

[edit]

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

[edit]

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

[edit]

Structure

[edit]

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.

Components

[edit]

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.[15][16]

Tiers of Frameworks
Tier 1 – Mostly depend only on Qt, highly portable
Tier 2 – Depends on Tier 1, but dependencies are still manageable.
Tier 3 – Complex dependencies, including Tiers 1–2 etc.
Tier 4 – Mostly plugins that provide additional features like platform support can be ignored.

Kirigami

[edit]

Kirigami is a QML application framework[18] developed by Marco Martin[19] 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,[20] the Kaidan messenger,[21] Vvave music player and the KDE software center Discover.

Software packages

[edit]

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

Bindings

[edit]

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

  • 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).[26]

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

[edit]
See also: KDE Software Compilation § Release cycle

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

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,[30] an example being better integration of Firefox into KDE.[31]

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.

As part of the KDE project's 'MegaRelease 6', on February 28, 2024, KDE Frameworks 6 was released, upgrading it to a Qt 6 base.[32]

KDE4 transformation

[edit]

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.[33]

Adoption

[edit]

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

[edit]
  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. Archived from the original on 11 July 2016. Retrieved 10 July 2016.
  3. ^ "Android - KDE Community Wiki". Archived from the original on 2016-08-26. Retrieved 2016-07-11.
  4. ^ "KDE API Homepage". Archived from the original on 2016-08-26. Retrieved 2016-07-11.
  5. ^ "First release of KDE Frameworks 5". 2014-07-07. Archived from the original on 2015-09-05. Retrieved 2014-07-08.
  6. ^ "The KDE Frameworks". API Documentation. Archived from the original on 2019-12-07. Retrieved 2020-03-17.
  7. ^ "KDE Frameworks". Tech Base. Archived from the original on 2020-08-13. Retrieved 2020-03-17.
  8. ^ a b c Howard Chan (2013-09-04). "KDE Release Structure Evolves". KDE. Archived from the original on 2020-11-12. Retrieved 2014-02-27.
  9. ^ "Release schedule for KDE Frameworks 5". Archived from the original on 2016-06-24. Retrieved 2016-05-18.
  10. ^ "Git workflow for Frameworks". Archived from the original on 2020-10-20. Retrieved 2014-08-19.
  11. ^ "KDE Frameworks5 API documentation". Archived from the original on 2014-08-22.
  12. ^ "Coinstallability with KDE Platform 4". Archived from the original on 2020-12-01. Retrieved 2014-08-19.
  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. Archived from the original on 2020-11-11. Retrieved 2014-03-10.
  15. ^ Howard Chan (2013-09-25). "Frameworks 5". Dot.kde.org. Archived from the original on 2020-11-26. Retrieved 2014-03-10.
  16. ^ "API Documentation". api.kde.org. Archived from the original on 2021-10-02. Retrieved 2021-10-02.
  17. ^ "KWindowSystem in Frameworks 5". 6 February 2014. Archived from the original on 28 July 2014. Retrieved 25 July 2014.
  18. ^ "KDE Kirigami". KDE. Archived from the original on July 29, 2019. Retrieved November 25, 2018.
  19. ^ "Contributors to KDE/Kirigami". GitHub. Archived from the original on 2019-04-30. Retrieved 2021-08-08.
  20. ^ Archived at Ghostarchive and the Wayback Machine: "Banji (Ring-KDE) new skin on desktop Linux and Android". YouTube.
  21. ^ "Kaidan - A user-friendly XMPP client for every device!". GitHub. 4 July 2021. Archived from the original on 26 April 2019. Retrieved 8 August 2021.
  22. ^ "KGlobalAccel in Debian". Archived from the original on 2016-09-20. Retrieved 2016-09-11.
  23. ^ "KGlobalAccel in Fedora".[permanent dead link]
  24. ^ "The KDE development platform". Archived from the original on 2018-10-03. Retrieved 2010-11-26.
  25. ^ Development/Languages - KDE TechBase Archived 2021-02-03 at the Wayback Machine. Techbase.kde.org (2012-07-12). Retrieved on 2013-07-17.
  26. ^ "Qyoto". Archived from the original on 2020-11-27. Retrieved 2015-01-18.
  27. ^ "Frameworks 5 Technology Preview". KDE. 2014-01-07. Archived from the original on 2014-02-26. Retrieved 2014-02-27.
  28. ^ "KDE Ships First Alpha of Frameworks 5". KDE. 2014-02-14. Archived from the original on 2014-03-01. Retrieved 2014-02-27.
  29. ^ "KDE Ships Second Alpha of Frameworks 5". KDE. 2014-03-03. Archived from the original on 2014-03-09. Retrieved 2014-03-04.
  30. ^ "KF5 Update Meeting Minutes 2014-w28". 2014-07-08. Archived from the original on 2016-03-07. Retrieved 2014-07-10.
  31. ^ "Firefox + KDE integration: Getting FF to use Dolphin reliably". 2014-07-03. Archived from the original on 2018-05-15. Retrieved 2014-07-10.
  32. ^ "KDE MegaRelease 6 Announcement". 2024-02-28. Retrieved 2024-03-20.
  33. ^ "KDE Licensing Policy". Archived from the original on 2010-12-16. Retrieved 2010-11-06.
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=KDE_Frameworks&oldid=1233713268"