Catching up with KDE
Manufacturer: The KDE Project
E-mail: firstname.lastname@example.org (users' mailing list subscription)
Price: Free Download
Reviewer: Robert Flemming
KDE developers may be one step closer to “konquering” the desktop with the most recent 2.1.1 release of the K Desktop Environment (http://www.kde.org/). The development cycle has intensified since the 1.0 series, bringing new features and stability improvements to users at an ever-increasing rate. In fact, as of this writing, the first alpha version of KDE 2.2 has been released for testing. End users and developers alike will benefit from the newest offering. Currently supporting 34 languages, KDE is poised to answer many of the questions surrounding Linux' viability on the desktop.
In addition to stability enhancements, the latest release includes a large number of cosmetic improvements that create a more unified and polished interface. Kicker, the 2.0 replacement of KPanel, received a number of new features as well as the return of an old one. For all of those WindowMaker users who just can't bare to part with their beloved dock applets, yearn no more. Kicker is now able to swallow your favorite applets into a new dock application bar (see Figure 1). Support has also been added for child panels, and the external taskbar noticeably absent from version 2.0 has returned, along with theme manager. Despite the re-inclusion of the theme manager, a lack of integration between the various theme-able elements of the desktop is still present. Widget styles, icons, colors, backgrounds and KWin decorations each need to be managed from their own individual Control Center modules. The work of the KDE artists team is not be overlooked, however. A number of icons were added and improved, and the new splash screens serve to unify desktop applications (see Figure 2).
Perhaps one of the most significant advances in the latest version is anti-aliased font support. In order to enable anti-aliased fonts, KDE must be built upon QT 2.3, in combination with XFree86's Xft extension. Linux has been somewhat plagued by issues regarding true-type fonts and anti-aliasing; while these advances greatly improve that, setting up anti-aliased fonts can be a bit of a challenge. Instructions can be found at trolls.troll.no/~lars/fonts/qt-fonts-HOWTO.html. If you installed KDE via packages, it may not have been built using the necessary libraries. If this is the case, you should check for newer package versions prior to trying to configure anti-aliased fonts. Figure 3 shows an enlarged comparison view of a web page as viewed from within Konquerer with anti-aliased font support and Netscape without anti-aliased font support.
The mechanisms by which Konquerer becomes more of an application framework than a file manager or web browser are called IO Slaves. IO Slaves are small bits of code based on the KIO library that know how to send and receive data using a specific protocol. From its inception KDE has focused on network transparency, and the KIO architecture has allowed for the creation of a variety of special purpose plugins that enhance the capabilities of Konquerer. Seamless support exists for browsing the Linux filesystem, NFS shares, MS Windows shares, web pages, FTP sites and LDAP directories, to name only a few. With a minimal amount of code, developers can make available new protocols and conduits to all KDE applications. Some of the other IO Slaves developed or being developed include digital camera support via Gphoto2, which allows for drag-and-drop access to images stored on your digital camera, and enhancements to the existing audiocd plugin that allow for drag-and-drop CD ripping and MP3/Ogg Vorbis encoding. Many of Konquerer's IO Slaves exist without much fanfair, yet are quite useful. For example, entering man:/df" or "#df into Konquerer will produce the man page for df (or other command of your choosing). For those preferring the GNU Info documentation browser, give info:/df a try. For quick access to your floppy drive, enter floppy:/ into the location bar. Another little-known addition to Konquerer is the new shell command function. For example, while browsing a directory via Konquerer, pressing Ctrl-e and entering a shell command like du will present the user with a dialog box displaying the output of the command in the currently viewed directory. A list of currently installed IO Slaves is available via the information section of the control center.
One particular IO Slave recently introduced pertains to LAN browsing. Those coming from a Windows background will most likely compare this to the Network Neighborhood. At the heart of this new feature is LISa, or the LAN information server. Unlike the Windows' Network Neighborhood, LISa only relies upon the TCP/IP stack and no other protocols such as SMB or NetBIOS. In short, once you configure LISa with information about the network to which you are attached, it will probe devices found on the network for commonly available services, such as FTP, SMB, NFS and HTTP (see Figure 5). By entering lan:/ into Konquerer, you will be presented with a list of all discovered servers and their associated services. While it may sound like LISa would create a lot of unnecessary network traffic, that is not the case. In fact, the more clients you have on your network running LISa, the more efficient it should become. LISa itself is a dæmon that runs on the client. Upon startup, that dæmon sends out a broadcast in an attempt to discover already existing LISa servers on the network. In the event that one is found, the network servers list is transferred to the new client without unnecessary network probing. At any given point in time, there should be only a single LISa node on the network doing the actual probing. LISa needs to be run as root and can be configured via the Network/LAN browsing control center module. LISa is a component of the kdenetwork package.
For the developer, KDE provides a rich set of tools for application development. Among these technologies are the desktop communication protocol (DCOP), a component object model (KParts), an XML-based GUI class and the previously mentioned I/O libraries (KIO). Tying all of these various [development] tools back into the desktop is the coordinated release of KDE's advanced IDE/RAD, KDevelop 1.4. Multimedia components are handled via an architecture built upon the network-transparent analog real-time synthesizer (aRts).
DCOP is the much talked about client-to-client communication protocol that replaced CORBA early on in the 2.0 development cycle. DCOP is built upon the standard X11 ICE library and presents a faster and more lightweight interface than what was previously being developed with CORBA. KParts, KDE's component object model, is what allows applications to share components and embed themselves within one another. The most extensive use of this technology can be seen in KOffice and Konquerer. Utilizing XML as a method of creating GUI elements dynamically, developers are able to provide a more customizable and standardized desktop interface. To aid desktop constancy, KDE has worked at establishing coding standards and a GUI styleguide. Since GUI elements are generated dynamically, updates to the styleguide are reflected immediately across GUI elements without recompilation or modification. aRts utilizes a CORBA-like network design enabling remote applications to output sound to the local workstation, providing a multimedia compliment to the network-transparent features provided by XFree86 and KIO. For more information on KDevelop or KDE application development, see the KDevelop 1.4 review on page xx. A wealth of developer-related information, including tutorials, FAQs and standards guides, can be found at http://developer.kde.org/.
It's astonishing to think of the strides Linux has made as a desktop operating system over the past few years, and the latest offering from the KDE camp is indeed a testament to this progress. With the emergence of new companies, as well as older, more established ones, focusing on improving and providing applications for the Linux desktop, greater acceptance is likely not far behind. The Kompany (http://www.thekompany.com/) has been turning out an amazing number of much-needed Linux applications. IBM has been working with Trolltech on integration of their ViaVoice software into QT to provide speech recognition to Linux users. KDE development as a whole is moving at a rate faster than ever before. Each release brings Linux one step closer to coming out of the data-center and onto the desktop.
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
|Introduction to MapReduce with Hadoop on Linux||Jun 05, 2013|
|Android's Limits||Jun 04, 2013|
- Containers—Not Virtual Machines—Are the Future Cloud
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Linux Systems Administrator
- Introduction to MapReduce with Hadoop on Linux
- Senior Perl Developer
- Technical Support Rep
- Weechat, Irssi's Little Brother
- UX Designer
- One Tail Just Isn't Enough
- Android's Limits
- Reply to comment | Linux Journal
27 min 29 sec ago
- Reply to comment | Linux Journal
27 min 56 sec ago
- Replica Watches
2 hours 52 min ago
- Reply to comment | Linux Journal
7 hours 3 min ago
- on the path to understanding
7 hours 7 min ago
- As a fisher,we know that a
1 day 2 hours ago
- All I Say Is Worth Share!
1 day 3 hours ago
1 day 3 hours ago
1 day 7 hours ago
- You should consider visiting
1 day 8 hours ago
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?