Slashdot Mirror
Ars Technica: Deep Inside KDE 3.2
binner writes "Ars Technica features an article 'Deep inside the K Desktop Environment 3.2' written by Datschge and Henrique Pinto. After introducing KDE and the project's structure the authors present some new applications of KDE 3.2. After that they explain the key KDE technologies KParts, DCOP, KIO, Kiosk and KXMLGUI and give examples for code reusage and an overview of efforts to integrate non-KDE applications. For developers Umbrello, Cervisia and Valgrind with KCachegrind are introduced and of course KDevelop 3.0. An examination of licenses precedes the positive conclusion."
The best thing about KDE is not the window manager/panel, but the application framework, like the technologies discussed in the articles. If you don't like the feel of KDE, you can always run fluxbox, but use KDE apps like Quanta, Konqueror, KDevelop and the likes. I've done that with Afterstep and WindowMaker as I'm not a fan of KWin.
I'm wondering if maybe kde might be or might become the killer app for Linux? I know that anyone who happens to glance at my 3.2 desktop always asks, "Wow, what's that?". It's no longer, "Hey is that a mac?" or "How did you get XP to look like that?". I think KDE has something going that no other desktop has. It has features that are all it's own, that aren't simply attempts at copying features of other desktops.
As a long time Gnome user, and as someone who will go on record as disliking Trolltech and their business model, I must say I am extremely impressed with KDE 3.2. Whilst I still think there is some tidying to go WRT options dialog boxes, this release strikes me as a massive leap forward. The new features and the improvements to Konqueror and the Kicker and so forth are really impressive. So much so, for the first time ever I spent the day working in KDE instead of Gnome and actually enjoyed it, rather than being constantly frustrated by inconsistencies and the general looks of the desktop.
Plastik is the first theme I've seen that makes KDE really start to look like a professional desktop rather than a mish-mash of poorly concieved applications. The underlying framework (KParts, kioslaves) and QT have always been superior to Gnome's, that much I'll admit. I still think it's a shame that QT is licensed under the GPL rather than a BSD-style license, but I guess I'll live.
I might even switch permanently if KDE 3.3 brings as many improvements.
I don't mean to be rude, but do you understand the difference between a desktop environment and a window manager? KDE is the former, Fluxbox the latter. They are two entirely different beasts. You can still run KDE or Gnome applications under any window manager. I run mine under Window Maker. To be fair, you're not the only one giving this sort of advice. I see it every time a Gnome or KDE story comes up, but it's annoyed me enough now that I just have to speak up.
The GNOME changes have nothing to do with assuming users are idiots. They have to do with cleanliness. I'm a developer, and I understand what just about any GUI option you throw at me does, or am quite capable of figuring it out. That doesn't mean I want to wade thru page after page after page of options which have no relation to what I want to do to find the one option I'm looking for.
:)
The GNOME changes are not dumbed down, they're cleaner. Advanced users are still quite capable of changing a plethora of options, using advanced methods. Only the very commonly changed options are placed in the menues and config panels, which makes it dead easy for both novices *and* experienced users to tweak the common things.
So far as the gatuitious UI changes, there are clear advantages to the way GNOME has chosen to do things. The dialog button order is a favorite thing of people who wish to bash GNOME, and thus serve as an excellent example. The new button order is *easier* on people both physically and mentally. (location of button wrt mouse movements, location wrt eye movements, etc.)
Additionally, there are no "OK" buttons. If you find one, it's a bug. Which is great. If you see a dialog, what the hell does "OK" mean? You have to read the whole dialog. And deal with the fact that in some cases, "OK" is the safe option, while in others it's the dangerous option. Different apps would pop up dialogs with different OK/Cancel meanings for the same dialog action. (like quit without saving - does OK mean "OK, Save" or "OK, Quit" ?) GNOME solves the problem by mandating that you don't use OK, but put the actual action as the button label. "Save" or "Quit". Much, much harder to accidently click OK when you meant Cancel because the meanings for two apps are different.
Granted, the last bit can be done even with the Windows/KDE button order (i.e. [Save] [Cancel] vs [Cancel] [Save]), which is something I really wish both Windows/KDE would do. The GNOME/Mac ordering however makes for consistent button location, however, since the "positive" (most commonly used) button is always in the same location in the dialog, which (as mentioned above) is both easier and more efficient physically and mentally, for both novice and experienced users. KDE having the ability to change button orders (as I've been told it does) is definitely cool; it would be great if they defaulted to the more human-friendly GNOME/Mac order, and let users who refused to learn switch back to the classic order.
Lots of users and developers think the GNOME/Mac button order is "weird" because they're used to the Windows' way, but that kind of thinking doesn't ever foster improvements. Thankfully, GNOME, OS X, KDE, and most other modern desktops are willing to break the mold and do things differently, even at the risk of "confusing" users, for the sake of moving the GUI experience forward, and not keeping us all locked into Microsoft's (and others') design mistakes made a decade or more ago.
I don't claim that GNOME has things perfect. Far from it. Simply explaining the reasoning behind certain 'controversial' changes. Hopefully useful.
One of the best and most unappreciated features of KDE is it's inherit troll value.
I'm sorry to post such a blatantly inflammatory gripe, and please don't reply to it in kind. Just be aware that the whole KDE vs. Gnome conversation is quickly degrading to the same sort of drivel that existed in the vi vs. emacs, gui vs. cli, X vs. Y debates.
Both KDE and Gnome are reasonably good programming environments (meaning I can program in both without requiring corrective surgery or extreme pain) and they both do a good job of managing, unifying, homogenizing, and (whatever) of the desktop.
If they come from two licensing lineages, so be it. I'm not worried about the environment / license you are going to choose, I'm going to choose the one I feel most comfortable with and has licensing (at cost or otherwise) that allows me to use it as I need. I'll assume you will do the same.
Less "better than Gnome!" or "worse than Gnome!" and more "it's really great that it has cleaned up feature X" please.
I apologize for such a rant, thank you for putting up with it.
imo the KDE people should take a step back and see what they're doing. all those pretty menus and shiny lights and a multitude of buttons and applets. neat, but useless. instead of new features (which KDE has enough already) they should focus more on the interface and how to make it more efficient.
:-)
If you were to read the article, and read the press announcements that came with KDE 3.2, and indeed try KDE 3.2, you'd find that they have done just that, as well as provide interesting new features. For example:
- KWallet, a new feature but one that makes using passwords and secure form data anywhere in the system much more efficient
- Cleaning up of lots of right click menus
- Cleaning up and improving kmenu
- Improving tabs in Konqueror
- A new universal side bar, which apparently is a lot more efficient for some people
- Even better integration of existing KDE technologies like klipper and kio_slaves into many KDE applications
The list goes on and on, but mostly they are small changes so you either have to use it to notice, or read through CVS changelogs. Next time I suggest you check before making loud statements like that