Linux: The Ultimate Guide

Window Management
• Box switch
• Cover switch
• Desktop cube
• Desktop Cube Animation
• Desktop Grid
• Flip switch
• Present windows
• Resize window
KHTML – HTML Rendering Engine, Installed on WebKit in 2004
KHTML is a browser engine built by the KDE project. It is the default 
engine of the Konqueror browser, but it has not been used since 2016. In 
addition, KHTML will be discontinued in KDE Frameworks 6.

---

KDE Plasma Desktop Environment 
◾
31
Built on the KParts framework and written in C ++, KHTML has 
excellent support for Web standards during its first season. The HTML 
rendering engines are used by some of the world’s most widely used brows-
ers, including Google Chrome, Safari, Opera, Vivaldi, and Microsoft Edge.
The following levels are supported by KHTML engine.
• HTML 4.01
• HTML 5 support
• CSS 1
• CSS 2.1 (screen and cached media)
• CSS 3 selectors (fully from KDE 3.5.6 [15])
• CSS 3 Other (multiple background, box size and text shadow)
• PNG, MNG, JPEG, GIF image formats
• DOM 1, 2 and section 3
• ECMA-262/JavaScript 1.5
• Scalable Vector Image Support Part
KJS – JavaScript Engine
KJS is a KDE ECMAScript-JavaScript engine developed by the KDE 
project web browser by Harri Porten in 2000. On June 13, 2002, Maciej 
Stachowiak announced in the mailing list that Apple was releasing 
JavaScriptCore, a KJ OS-based Mac OS X framework. With the WebKit 
project, JavaScriptCore has been transformed into SquirrelFish Extreme, 
a JavaScript engine that integrates JavaScript into native code.
KIO – Expandable Network File Access
KIO (short for KDE Input/Output) is part of the KDE architecture. It pro-
vides access to files, websites, and other resources with a single fixed API. 
Applications, such as Konqueror, written using this framework, can work 
on files stored on remote servers in the same way they work on local stor-
age, effectively making the KDE network visible. It allows the file browser 
as Konqueror, the most flexible and powerful file manager, and web 
browser. KIO can support individual protocols (e.g., HTTP, FTP, SMB, 
SSH, FISH, SFTP, SVN, TAR). The KDE Khelp Help Center application 
has a kioslaves section that lists available terms briefly.

---

32
◾
Linux 
KParts – Frame Part of an Image within a Lightweight Process
KPart technology is used in KDE to re-use GUI components. The advan-
tage presented by KPart is that it comes with predefined toolbar actions. 
By using KPart in applications, developers can spend less time using a text 
editor or command-line features, for example, and use katepart or kon-
solepart instead. KParts is also used with plugin technology to embed 
applications within one another, such as integrating PIM applications into 
Kontact.
XML GUI
XML GUI is a KDE framework for designing user interaction applications 
using XML, using action concepts. In this framework, the editor designs 
actions that his application can use, with a few actions defined by the edi-
tor in the KDE framework, such as opening a file or closing an applica-
tion. Each action is associated with various data, including thumbnails, 
captions, and tips.
An exciting part of this design is that the actions are not included in the 
menus or toolbar by the editor. Instead, the editor provides an XML file 
explaining the menu bar and toolbar layout. By using this application, the 
user can rearrange the user interface without having to touch the source 
code of the application in question.
In addition, XML GUI is useful for the KParts component interface 
of the KDE component, as the application can easily integrate the KPart 
GUI into its GUI. Konqueror file manager is a canonical example of this 
feature. The current version is KDE Frameworks # KXMLGUI.
Phonon – Multimedia Framework
Phonon is a multimedia API provided by KDE and is a standard summary 
for managing multimedia streaming within KDE software and is used by 
several Qt applications. Phonon was created to allow KDE and Qt software 
to be independent of any single multimedia framework such as GStreamer 
or xine and provide a stable API for the life of the prior version. It is done 
for various reasons: to build a KDE/Qt-style multimedia API, better sup-
port native multimedia frameworks for Windows and macOS, and fix 
framework issues that may be neglected or have API or ABI instability.
Solid – Device Assembly Frame
Solid is a device integration framework. It provides a query and hard-
ware interface outside of the underlying operating system. It provides the 

---

KDE Plasma Desktop Environment 
◾
33
following features for application developers: Hardware Discovery, Power 
Management, and Network Management.
Sonnet
Sonnet is a spell-checking library based on Qt-based applications plugins. 
It supports several plugins, including HSpell, Enchant, ASpell, and hun-
spell. It also supports automatic language detection based on a combina-
tion of different algorithms.
ThreadWeaver
It is a system library developed initially for KDE Software Compilation 
4 and later redesigned in KDE Frameworks 5. It allows developers to use 
multi-core processors and multithreading easily. In ThreadWeaver, the 
workload is divided into individual tasks. Then, there is a relationship 
between functions. ThreadWeaver will use the most efficient way to use 
them. Krita used visual filtering preview using ThreadWeaver to disable 
GUI lock.
KDE APPLICATIONS
Critical applications created by KDE include:
Editors
• Kate: Advanced Text Editor for editors
• Kedit: A simple text editor with a few features, such as Windows’ 
Notepad
• Kile: LaTeX editor
• KWrite: Text editor
Education
• KGeography: An application that scans local information
• Kiten: A Japanese learning tool
• KLAid: A learning tool from cards while using a PC
• Konjue: A tool for compiling and compiling French verbs
• Kalzium: Displays information about the material table

---