Language Selection

English French German Italian Portuguese Spanish

Nine Improvements Needed in KDE

Filed under
KDE

KDE 4 is a radical overhaul of the popular desktop. It offers broad improvements like the Oxygen desktop theme, SVG graphics, and enhanced speeds thanks to the latest version of the Qt 4 toolkit. It also offers specific improvements such as the font manager and the Dolphin file manager. In short, there's a lot to like.

But, as might be expected, not all the changes are equally successful. Nor is the situation helped by the fact that KDE 4 was a preliminary release, and the project intends the upcoming 4.1 as the production-ready version -- as you might expect, most distros have rushed to include the early minor releases as soon as possible.
After a week of regularly using KDE 4.0.2 and 4.03 releases on my laptops, these are the improvements that would enhance KDE the most:

A more customizable panel

In the rush to get KDE 4 out the door on time, the first version came with an unresizable panel stuck firmly at the bottom of the screen.

More Here




More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more