Language Selection

English French German Italian Portuguese Spanish

KDE compositing in openSUSE11.1

Filed under
KDE
SUSE

As you might have noticed, KDE 4.1.3 has been released, codename "Change" (in line with other C- codenames recently, as a kind of a joke on all those people who fail to see that still writing comments with overuse of K after 10 years of KDE's existence can only be a sign of brain damage). Not many changes in KWin there though, the changelog part for KWin has just one change worth mentioning. But that is not the case for users of the openSUSE KDE:KDE4:Factory:Desktop packages, which are the packages that will be also used for openSUSE 11.1. This is because they include a special KWin branch, which contains both backports of various new features from other KWin developers from SVN trunk (Lucas' blog keeps track of many of those) that cannot be backported to the 4.1 branch by KDE rules but should be stable and safe enough, and new features developed specially for the needs of openSUSE11.1/SLED11.

The most prominent of these is probably the fact that compositing is going to be enabled by default if possible - that is, if you install openSUSE 11.1 on a system capable of decent compositing without explicit installation of drivers, you will get desktop effects out of the box.

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