Language Selection

English French German Italian Portuguese Spanish

KDE 4.2: Ten Tips for Getting Started

Filed under
KDE

Over the last year, the KDE 4 releases have suffered frequently hostile receptions. Part of that hostility was due to a widespread failure to understand that the first release was not intended for general use, and therefore was missing some of the features that KDE users took for granted. Another part seems to have been the sheer number and novelty of some of the changes. However, improvements and familiarity have taken much of the edge off the hostility, and, with last month's release of version 4.2, users finally seem to be warming to the new KDE.

All the same, KDE 4.2 is full of new design concepts and features that take a while to appreciate. Sometimes, these changes are simply a repositioning of familiar features; yet just as often, they represent a rethinking of everyday tools. Once or twice, the features even overlap or conflict with existing ones.

To help bring you up to speed, here are ten tips for understanding and working with KDE 4.2. They aren't exhaustive by any means -- but they should be enough to make you comfortable moving around KDE 4.2 so that you can discover other changes on your own.

1) Going in and out of customization display

Probably the first thing you should know about KDE 4 is that it has separate views for customizing desktop and panel options.

rest here




More in Tux Machines

Leftovers: Gaming

Leftovers: Software

today's howtos

ACPI, kernels and contracts with firmware

This ends up being a pain in the neck in the x86 world, but it could be much worse. Way back in 2008 I wrote something about why the Linux kernel reports itself to firmware as "Windows" but refuses to identify itself as Linux. The short version is that "Linux" doesn't actually identify the behaviour of the kernel in a meaningful way. "Linux" doesn't tell you whether the kernel can deal with buffers being passed when the spec says it should be a package. "Linux" doesn't tell you whether the OS knows how to deal with an HPET. "Linux" doesn't tell you whether the OS can reinitialise graphics hardware. Read more