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

Maui Weekly Report

There has been a lot of work into the Maui Project, and the Nitrux team has been actively working on the apps, the framework, and the libraries to make the convergence experience something unique and reliable for our first stable release. Since last time we posted something about the project, many things are refactored, a lot of improvements and UI/UX paper-cut fixes are introduced, and new platforms now have support. We were present at the Plasma Mobile sprint at Berlin, working on improving the Maui apps experience for such a platform. In the sprint, the UBPorts developers were also present, and we are looking forward to seeing the Maui Apps in their platform. Read more

COVID-19 +++ Global cooperation +++ Remote working

Free Software is the only solution to offer full transparency and trust in its implementation. More and more people ask about the use and development of apps that aim at helping to contain the corona virus by tracking new infections and their contact persons. The Free Software Foundation Europe demands that any such app may only be introduced on a voluntary basis and the software must be published under a Free Software / Open Source Software licence. Only Free Software offers enough transparency to validate a complete data protection and a compliant use; thus trust can be established. Read more

Games: Shadow Warrior 2, Golf With Your Friends and Kingdoms and Castles

  • Shadow Warrior 2 | Linux Gaming | Ubuntu 19.04 | Steam Play

    Shadow Warrior 2 running through Steam Play (Proton 5.0-4) Runs great, few stutters here and there.

  • The brilliant 'Golf With Your Friends' has another massive content update

    A good time for an update with ton of people at home, and what a great game to play with others too! Golf With Your Friends just recently had a 'Volcanic Update' with quite a lot of new content. With an entirely new volcanic and sci-fi themed 18 hole course, the Volcano enters the race. There's also a new Japanese translations, a new and improved Course Editor, new obstacles and hazards, a better tutorial and there's even gamepad support to make it more accessible than ever. [...] Just as a reminder, they announced recently that it was going to be leaving Early Access in Q2 this year, so presumably before the end of June and they've still got updates to come yet.

  • City-building strategy 'Kingdoms and Castles' adds Steam Workshop support ahead of AI kingdoms update

    Kingdoms and Castles, an absolute gem city-builder with some RTS elements to it just gained a highly requested feature with Steam Workshop support now enabled. Kingdoms and Castles can perhaps be compared with games like Banished, requiring you to plan ahead and make sure you have enough food to last through each winter. [...] This should, hopefully, keep players going until the massive AI kingdom update arrives sometime. That's going to be a massive change for the game, further expanding how you play and I'm super excited for it.

Mozilla: Volunteers, These Weeks in Firefox and Development Tales

  • Firefox 75 new contributors

    With the release of Firefox 75, we are pleased to welcome the 40 developers who contributed their first code change to Firefox in this release, 38 of whom were brand new volunteers! Please join us in thanking each of these diligent and enthusiastic individuals, and take a look at their contributions...

  • These Weeks in Firefox: Issue 72
  • Nick Desaulniers: Off by Two

    “War stories” in programming are entertaining tales of truly evil bugs that kept you up at night. Inspired by posts like My Hardest Bug Ever, Debugging an evil Go runtime bug, and others from /r/TalesFromDebugging, I wanted to share with you one of my favorites from recent memory. Recent work has given me much fulfilment and a long list of truly awful bugs to recount. My blog has been quieter than I would have liked; hopefully I can find more time to document some of these, maybe in series form. May I present to you episode I; “Off by Two.” [...] asm goto is a GNU C extension that allows for assembly code to transfer control flow to a limited, known set of labels in C code. Typically, regular asm statements (the GNU C extension) are treated as a black box in the instruction stream by the compiler; they’re called into (not in the sense of the C calling convention and actual call/jmp/ret instructions) and control flow falls through to the next instruction outside of the inline assembly. Then there’s an “extended inline assembly” dialect that allows for you to specify input and output constraints (in what feels like a whole new regex-like language with characters that have architecture specific or generic meanings, and requires the reference manual to read or write) and whether to treat all memory or specific registers otherwise unnamed as outputs as clobbered. In the final variant, you may also specify a list of labels that the assembly may jump control flow to. There’s also printf-like modifiers called Output Templates, and a few other tricks that require their own post. Within the compiler, we can’t really treat asm statements like a black box anymore. With asm goto, we have something more akin to structured exception handling in C++; we’re going to “call” something, and it may jump control flow to an arbitrary location. Well, not arbitrary. Arbitrary would be an indirect call through a pointer that could’ve been constructed from any number and may or may not be a valid instruction (or meant to be interpreted as one, ie. a “gadget.”) asm goto is like virtual method calls or structured expection handling in C++ in that they all can only transfer control flow to a short list of possible destinations.