Language Selection

English French German Italian Portuguese Spanish

KDE 4.0: Everything that has an end, has a beginning

Filed under
Reviews

Note: This review's based on KDE 4.0 installed on openSUSE 10.3. If you're running openSUSE 10.3, KDE 4.0 is extremely easy to install. (Apologies to the Wachowski brothers for the title.)

Get Over It

A confession: I was among the many who griped publicly (and privately) about KDE 4.0's release date. I thought KDE 4.0 was not ready for release and should be held back until it was. (Hey, my wife and my dog listened to me. So there.)

Why? There were two main reasons.

First, one of the things I've loved the most about KDE is its large range of configuration options. For example, there's about a gazillion things you can do with the "kicker panel" (a.k.a. the taskbar) at the bottom of the screen in KDE 3.5.7.


Some of KDE 3.5.7's many kicker configuration options

By comparison, there's little you can do with the panel in KDE 4.0 — and, compared to KDE 3.5.7, not a lot you can do with the desktop, either. It didn't help that the betas and release candidates of KDE 4 contained even less functionality than the final version.

Second, although I've been playing with Linux distros since the late 90s, I didn't start using Linux seriously until around 2003. So the only version of KDE that I learned well was KDE 3. Changes to the KDE 3.x series seemed incremental; in other words, if you ran a live CD containing KDE 3.0, you could definitely recognize it as the precursor to KDE 3.5.8. I assumed KDE 4's user interface (UI) would be a "superset" of KDE 3.x's.

Instead, the KDE developers chose to concentrate on rewriting KDE's "plumbing," focusing (as far as this non-developer can tell) on simplifying and modernizing KDE's application programming interfaces (APIs), and updating it to Qt 4 (Qt is the development framework that KDE's based on). Among other things, this new "plumbing" includes a multimedia back-end named phonon; a new way of dealing with hardware named solid; and, most noticeably, a new user interface named plasma. As its Wikipedia article notes, "Plasma is still undergoing heavy development."

(Long-time KDE users have already noticed that, for some strange reason, none of the names for these technologies begin with the letter "k.")

Wikipedia mentions that, in KDE "x.0" releases, the developers can break compatibility with former releases. They didn't go that far, since KDE 3.5.x apps seem to run just fine on KDE 4.0. But we did see an example of the open source mantra, "release early, release often," in action. And it's worth mentioning that, while still very rough around the edges, the released version of KDE 4.0 was greatly improved compared to the betas and release candidates.

Developers as Politicians

Something else happened that was interesting. Several KDE developers, realizing the controversy there would be over KDE 4.0's unfinished state, took the time to explain what was going on. In particular, Aaron Seigo, president of the KDE foundation and the man mainly responsible for Plasma, addressed naysayers in a long blog post titled "Talking Bluntly" (a recommended read). openSUSE's Stephan Binner wrote a couple of posts about the situation. As the openSUSE KDE 4 page says:

"To make a long story short: KDE 4.0 is not and never was meant to replace 3.5.x for regular users. The main goals were porting to Qt4 and creating the frameworks to create all the things announced for KDE 4. Frameworks are unfortunately hardly visible to the user, so most things that use them, like plasmoids, panel-functionality etc., will only appear after the frameworks are in place, i.e. starting with 4.1."

(If you've got the time and bandwidth, download and listen to The Linux Link Tech Show's Jan. 2nd interview with Aaron Seigo (link goes to a 33.8 MB audio file in ogg format). He comes across as a very intelligent, thoughtful guy, and does a great job explaining the decisions behind KDE 4. Mr. Seigo seems to have taken quite a bit of grief over Plasma, but handles criticism with aplomb. Calling someone a politician is not always an insult!)

From Kubuntu to KDE 4.0

Users of Kubuntu 7.10 "Gutsy Gibbon" were treated to a simplified file manager named Dolphin, a simplified control center named System Settings, and a web-based desktop search engine named Strigi. All three are in KDE 4.0. Moreover, Dolphin now plays the role of KDE's default file manager, and System Settings replaces the KDE Control Center.

   
Left: Dolphin and System Settings on Kubuntu. Right: Strigi desktop search on Kubuntu.

   
Dolphin, System Settings, and Strigi on KDE 4.0

KDE 4.0's user interface will seem familiar to users of former versions of KDE. The major change is the addition of so-called "widgets," or "plasmoids," to the desktop. (I'll use the terms interchangeably.) Widgets are usually SuperKaramba-like applets, which could potentially be anything from a clock to a calculator to a system monitor. But it goes further than that — even desktop icons are widgets.

     
The KDE 4.0 panel (itself a plasmoid), L-R: Kickoff menu; traditional menu; task manager; desktop pager; Klipper (in the System Tray); New Device Notifier; and clock

Desktop widgets can be added by mousing over the Plasma icon in the upper right-hand corner of the screen, or from a desktop context menu. If you want to add one to the panel (such as the "traditional menu" seen above, or a trashcan), you can click and drag them from the "Add Widgets" dialog to an empty spot on the panel. You can also filter your favorite widgets from that dialog, as well as take them off your desktop.

 
Miscellaneous widgets

 
Messing around with widgets (click for larger image)

Widgets can be rotated, made larger, configured (if there are any configuration options for that widget), and made to quit, via small icons in the frame surrouding them that shows up when you mouse over them. You can lock them to the desktop, which hides the frame (which is handy, because at this point, sometimes the frame doesn't go away when it should).

Essential Apps

It would seem that the KDE developers wanted users to be able to differentiate between the web browser (Konqueror) and the file manager (Dolphin), instead of having the confusion of having Konqueror perform both functions. Although you can still use Konqueror as a file manager (by pressing Alt+F2 to open KRunner, and entering the command "konqueror --profile filemanagement" as before), for now, Konqueror uses Dolphin as its file management engine. (What's missing in both is a tree view in the right-hand pane. Hopefully that'll come back soon.)

Dolphin seems to have borrowed from GNOME's Nautilus file manager and from Mac OS X in its design. Of particular interest: the "breadcrumb" bar across the top, between the toolbar and the file window. Click on a ">" symbol to get a vertical listing of directories. The "breadcrumb" bar can be interchanged with a regular editable location bar with a mouse click. Also of interest: the new "columns" and "split" views (which sort of make up for the lack of a tree view in the right-hand pane).

   
L-R: Dolphin with "breadcrumb" bar; Dolphin using column view; Konqueror in file management mode

KDE 4.0's new default document viewer, Okular, can open up a huge variety of document formats. Gwenview is KDE's default image viewer. Konsole, KDE's terminal application, has a subtly revamped feel. (I could swear the line spacing is just a bit larger than it was in KDE 3.5.x; a pleasant surprise.)

   
L-R: Okular's list of supported formats; Gwenview in browser mode; Konsole's "profiles" settings

Games in KDE 4.0 now usually use scalable vector graphics, for a much nicer look. There are some interesting new applications, including Marble, a searchable "desktop globe;" and KPhotoAlbum, which is apparently complicated enough that the new user's offered a 10-minute series of introductory videos. As of this writing, KOffice 2.0 is still under development, and while some parts of it work, others (such as KWord) instantly crash.

     
L-R: Games in KDE 4.0; the Marble desktop globe; KPhotoAlbum; the Amarok audio player (version 2.0 "pre-alpha")

More Eye Candy

KDE 4.0's default theme, named Oxygen, comprises a new set of default sounds, a new, more photo-realistic set of icons, a windows decoration, or "windec" (the part that surrounds your application windows), and a widget style ("widget," in this sense, meaning buttons, scroll bars, progress bars, etc.).

(For those keeping score, most of these screenshots use Plastik as the windec and (the new) Plastique as the style. You still get to choose.)

   
The Oxygen style

If you've got a graphics card capable of displaying compositing effects (such as you'd see with Compiz Fusion), you'll find that KDE 4.0 includes many of its own. (They're turned off by default, but can be switched on from System Settings > Desktop > Desktop Effects.) Some of the effects are quite useful, such as the one that darkens the window underneath an active dialog box; and some are just for fun, such as the Explosion effect that makes windows that are closed, explode into pieces. Be advised that, at this point, turning on desktop effects can make other applications unresponsive, cause general flakiness, and make the entire UI unresponsive if you use an OpenGL screensaver.


     

L-R: Desktop effects settings; an Alt+Tab "box switch" window switcher; a "desktop grid" virtual desktop chooser

Finally, KDE 4.0 also comes with some gorgeous wallpapers.

In Conclusion...

KDE 4.0's release has been a learning experience, at least for me. KDE 4.0's got a long ways to go before it's ready to replace KDE 3.5.x. (For example, my desktop icons have suddenly stopped working!) But one thing is for sure: improvements (which is what you'll call them if you approve of them) and changes (which is what you'll probably call them if you don't) are occurring rapidly. (It seems like openSUSE releases new KDE 4 packages on an almost daily basis.) As far as the prior complaints go — fuggeddabouddit. Time to move on. I'm looking forward to seeing what KDE looks like, six months from now, and longer-term, years from now.

— Andrew Heil, aka "eco2geek"

For More Information:




StumbleUpon


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

A Fair Summary

My experience has been similar. I do remember one slightly angry diatribe by Aaron Segio in early beta days on his blog in response to some criticism. It appears to me that Mr. Segio has matured and grown in this development/release process. He is certainly a bright, thoughtful, and engaging person as his appearance on the TLLTS podcast clearly demonstrates.

I look forward to KDE 4.1 and 4.2, as I do believe that it will make for a magnificent desktop experience.

> KDE 3.5.x apps seem to run

> KDE 3.5.x apps seem to run just fine on KDE 4.0

That's because they use Qt4, whereas KDE4 uses Qt4, so I suppose KDE3-apps don't actually use anything from KDE4!

Makes sense

And since openSUSE puts KDE3 into /opt, and KDE4 into /usr (which is where all the other distros I've seen usually put KDE3), that probably makes it a whole lot easier to have them both installed at the same time, without naming conflicts.

s/Qt4/Qt3/

Béranger wrote:
That's because they use Qt4, whereas KDE4 uses Qt4
Obviously, what I wanted to say is "because they use Qt3, whereas KDE4 uses Qt4".

Nice summary Eco2geek.

I too was one of the ones that complained alot about the kde 4 rc/betas. I still feel there's alot of missing functionality and such..but overall, I was actually a lot LESS disappointed with kde 4.0 than I thought I would be. Some how..it seems they really made everything fall into place right before the release. I've been using it ever since..and aside from a few minor annoyances, it's a fairly solid desktop. I really like it..and I'm looking forward to future releases..which should be greatly improved feature-wise.

More in Tux Machines

Today in Techrights

Programming Leftovers

  • ThreatMapper: Open source platform for scanning runtime environments - Help Net Security

    Deepfence announced open source availability of ThreatMapper, a signature offering that automatically scans, maps and ranks application vulnerabilities across serverless, Kubernetes, container and multi-cloud environments.

  • Josef Strzibny: Organizing business logic in Rails with contexts

    Rails programmers have almost always tried to figure out the golden approach to business logic in their applications. From getting better at object-oriented design, to service objects, all the way to entirely new ideas like Trailblazer or leaving Active Record altogether. Here’s one more design approach that’s clean yet railsy.

  • Status update, October 2021

    On this dreary morning here in Amsterdam, I’ve made my cup of coffee and snuggled my cat, and so I’m pleased to share some FOSS news with you. Some cool news today! We’re preparing for a new core product launch at sr.ht, cool updates for our secret programming language, plus news for visurf. Simon Ser has been hard at work on expanding his soju and gamja projects for the purpose of creating a new core sourcehut product: chat.sr.ht. We’re rolling this out in a private beta at first, to seek a fuller understanding of the system’s performance characteristics, to make sure everything is well-tested and reliable, and to make plans for scaling, maintenance, and general availability. In short, chat.sr.ht is a hosted IRC bouncer which is being made available to all paid sr.ht users, and a kind of webchat gateway which will be offered to unpaid and anonymous users. I’m pretty excited about it, and looking forward to posting a more detailed announcement in a couple of weeks. In other sourcehut news, work on GraphQL continues, with paste.sr.ht landing and todo.sr.ht’s writable API in progress. Our programming langauge project grew some interesting features this month as well, the most notable of which is probably reflection. I wrote an earlier blog post which goes over this in some detail. There’s also ongoing work to develop the standard library’s time and date support, riscv64 support is essentially done, and we’ve overhauled the grammar for switch and match statements to reduce a level of indentation for typical code. In the coming weeks, I hope to see date/time support and reflection fleshed out much more, and to see some more development on the self-hosted compiler. [...] The goal of this project is to provide a conservative CSS toolkit which allows you to build web interfaces which are compatible with marginalized browsers like Netsurf and Lynx.

  • Monthly Report - September

    The month of September is very special to me personaly. Why? Well, I got married in the very same month 18 years ago. The best part is, I choose the day 11 to get married. I have never missed my wedding anniversary, thanks to all the TV news channel.

  • My Favorite Warnings: uninitialized | Tom Wyant [blogs.perl.org]

    This warning was touched on in A Belated Introduction, but I thought it deserved its own entry. When a Perl scalar comes into being, be it an actual scalar variable or an array or hash entry, its value is undef. Now, the results of operating on an undef value are perfectly well-defined: in a nuneric context it is 0, in a string context it is '', and in a Boolean context it is false. The thing is, if you actually operate on such a value, did you mean to do it, or did you forget to initialize something, or initialize the wrong thing, or operate on the wrong thing? Because of the latter possibilities Perl will warn about such operations if the uninitialized warning is enabled.

today's leftovers

  • CutefishOS Built on Ubuntu Run Through - Invidious

    In this video, we are looking at CutefishOS Built on Ubuntu.

  • CutefishOS Built on Ubuntu

    Today we are looking at CutefishOS Built on Ubuntu. It comes with Linux Kernel 5.11, based on Ubuntu 21.10, and uses about 900MB of ram when idling. Enjoy!

  • Google adds VM support to Anthos, admits not everyone is ready for containerised everything [Ed: Kubernetes becoming increasingly just an openwashing shim for proprietary software with back doors]

    Google has added support for workloads running in virtual machines to its Anthos hybrid Kubernetes platform. "While we have seen many customers make the leap to containerization, some are not quite ready to move completely off of virtual machines," wrote Google Application Modernization Platform vice-presidents Jeff Reed and Chen Goldberg. "They want a unified development platform where developers can build, modify, and deploy applications residing in both containers and VMs in a common, shared environment," the pair added.

  • The Dell Inspiron 15 3501 supports Linux

    With the Inspiron 15 3501, Dell has a 15.6-inch office laptop in its lineup with its technology housed in a slim, matte-black plastic case. The chassis lacks stability: The lid and the base unit in particular can be twisted a bit too much. The matte display (Full HD, IPS) offers stable viewing angles, good contrast, and decent color reproduction. However, the brightness and color-space coverage are too low. The built-in combination of the Core i7-1165G7 processor, 16 GB of RAM (dual-channel mode), and a 512 GB NVMe SSD (M.2 2230) equips the laptop for office and Internet applications. If the storage space isn't enough, an additional 2.5-inch storage drive can be installed. You can also replace or expand the RAM.

  • Linux Foundation raises USD 10 mln to secure software supply chain
  • ISO establishes SBOM standard for open source development with SPDX

    You’re not getting attention because of your choice of text editor or the number of spaces you use to indent code blocks. However motivating those preferences are for you and me, the non-technical world sees them as private choices. You find your code in the headlines for a different and unpleasant reason: open source dependency management.

  • Printed Piano Mechanism Sure Is Grand | Hackaday

    Do you know how a piano works? Sure, you press a key and a hammer strikes a string, but what are the finer points of this operation? The intricacy of the ingenious mechanism is laid bare in [Mechanistic]’s 3D-printed scale model of a small section of the grand piano keyboard. The ‘grand’ distinction here is piano length-agnostic and simply refers to any non-upright. Those operate the same way, but are laid out differently in order to save space.

  • FPGA Boards Add VGA And HMDI Interfaces To The Original Game Boy | Hackaday

    The classic Game Boy remains a firm favorite in the realm of retrocomputing. Revolutionary as it was at the time, by today’s standards its display is rather primitive, with no backlight and a usable area measuring only 47 mm x 44 mm. [Martoni] figured out a way to solve this, by developing GbVGA and GbHdmi, two projects that enable the Game Boy to connect to an external monitor. This way, you can play Super Mario Land without straining your eyes, and we can also image potential uses for those who stream their gameplay online.

  • Art Project Fast And Fouriously Transforms Audio Into Eye Candy | Hackaday

    The overall build is relatively simple. Audio is acquired via a line-in jack or a microphone, and then piped into an ESP32. The ESP32 runs the audio through the FFT routine, sampling, slicing, and dicing the audio into 16 individual bands. The visual output is displayed on a 16 x 16 WS2812 Led Matrix. [mircemk] wrote several routines for displaying the incoming audio, with a waterfall, a graph, and other visualizations that are quit aesthetically pleasing. Some of them are downright mesmerizing! You can see the results in the video below the break.

IBM/Red Hat Leftovers

  • Reach your open source community with content marketing [Ed: IBM has totally lost direction; this is how they think of Free software...]

    Both startups and more established firms are increasingly turning to content marketing as a way of reaching prospective customers. However, corporate marketers often consider the open source software (OSS) community a challenge to reach. This article features ways your technology and content marketing teams can work together to target and reach the community around an OSS project your organization supports.

  • Why digital transformation demands a change in leadership mindset

    Recently a key retail executive forecast that their industry will change more in the next five years than it has in the past fifty. Another executive believes society will change more in the next fifty years than it has in the last three hundred. A recent headline declared that, “We are approaching the fastest, deepest, most consequential technological disruption in history”, and Ray Kurzweil, Google’s Director of Engineering and co-Founder of Singularity University, has said that there will be fourteen internet size revolutions in the next decade. Whichever way you look at it, things are shifting… fast. When you speak with the visionaries and entrepreneurs actually building the solutions of tomorrow, from on-demand retail to vertical farms, and ask how far into this new era we are, almost universally the reply is: “only one percent”. Imagine then, where we will be ten years from now? How about 50? Major industries, from medicine to energy to travel to entertainment, are radically transforming, putting pressure on others such as manufacturing, construction, transportation, finance, education…frankly, all of it. What an extraordinary opportunity this presents.

  • DevSecOps lessons learned during a pandemic | The Enterprisers Project

    As we’ve seen over the past year and a half, the pandemic has accelerated digital transformation and forever changed workplace culture. Increased reliance on digital tools has elevated the value of DevSecOps, as enterprises of all sizes and across all industries realize the importance of automating and integrating security at every phase of the software development lifecycle – from initial design through integration, testing, deployment, and product delivery. My engineering team was no exception to this shift – we had to quickly prepare to build a new Virtana SaaS platform and deliver several new modules, all while working remotely. Here I’ll share some observations, pain points, and lessons learned to help others intelligently embrace DevSecOps best practices within their teams.