KDE Platform 4

KDE Platform 4 was a collection of libraries and software frameworks by KDE that served as technological foundation for KDE Software Compilation 4 distributed under the GNU Lesser General Public License (LGPL). KDE Platform 4 was the successor to KDElibs and the predecessor of KDE Frameworks. KDE Platform 4 is the only version of KDE Platform, see KDE’s brand repositioning.

KDE Platform 4
Original author(s)KDE
Developer(s)KDE
Initial release11 January 2008 (2008-01-11)[1]
Final release4.14.12 (September 15, 2015 (2015-09-15)) [±][2]
Repository
Written inC++[3][4]
Type
LicenseGNU Lesser General Public License (LGPL)

Technologies

  • User Interface
    • Plasma – desktop and panel widget engine
    • KHTML – HTML rendering engine
    • KIO – extensible network-transparent file access
    • KParts – lightweight in-process graphical component framework
    • Sonnet – spell checker
    • XMLGUI – allows defining UI elements such as menus and toolbars via XML files
    • Goya
  • Hardware and Multimedia
    • Phonon – multimedia framework
    • Solid – device integration framework
  • Services
    • NEPOMUK
    • KNewStuff – KDE's "Hot New Stuff" classes
    • Policykit-KDE
  • Communication
  • Games
    • Gluon
    • KGGZ
  • Other
    • ThreadWeaver – library to use multiprocessor systems more effectively
    • Kiosk – allows disabling features within KDE to create a more controlled environment
    • Kross
    • KConfig XT
    • WebDAV

Technologies superseded in KDE Platform 4

KParts

KParts is the component framework for the KDE Plasma desktop environment. An individual component is called a KPart. KParts are analogous to Bonobo components in GNOME and ActiveX controls in Microsoft's Component Object Model. Konsole is available as a KPart and is used in applications like Konqueror and Kate.

Example uses of KParts:

External links

Solid

Solid is a device integration framework for KDE Platform 4 and its successor, KDE Frameworks. It functions on similar principles to KDE's multimedia pillar Phonon; rather than managing hardware on its own, it makes existing solutions accessible through a single API. The current solution uses udev, NetworkManager and BlueZ (the official Linux Bluetooth stack). However, any and all parts can be replaced without breaking the application, making applications using Solid extremely flexible and portable.[5][6] Work is underway to build a Solid backend for the Windows port of KDE based on Windows Management Instrumentation.[7]

Solid is broken up into many hardware “domains” which operate independently. Domains may be added as needed. For instance, one domain may be Bluetooth, and another may be power management. Solid is used extensively within KDE 4 and its popular applications, making them more aware of hardware events and easier to develop.

External links

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.