KDE 4 Preview
KDE 4, first announced two years ago, is the next step for the popular UNIX desktop environment. With the shift to a new major version of the toolkit used to build KDE, developers are able to break free of requirements for compatibility and make radical changes to the codebase.
Qt 4
Qt 4 is a library for building user interfaces in C++. It provides most of the graphical elements of KDE applications.
Qt 4 heralds vastly better memory efficiency and a new painting system that is able to leverage new advances in X.org for previously unseen levels of eye candy. It also provides, for the first time, a GPL'd version of the library on Apple's OS X and Microsoft's Windows, making porting KDE applications to other platforms a possibility.
The default desktop infrastructure, well remembered as operating on similar lines since KDE 2, is being completely redesigned. The new desktop shell, Plasma, promises to re-invent the desktop paradigm. Headed by Aaron Siego, Plasma's team of developers has been working on a complete replacement for the previous infrastructure of the KDE panel and desktop, and the results are breathtaking.
Plasma incorporates most of what is seen on screen at first login. It is a flexible, fully scalable and rotatable desktop shell with the ability to embed mini-applications and media as applets or widgets known as plasmoids. The concept of applets is not a new one to desktop design, but Plasma brings a few innovations to the table.
Plasma divorces the data engine from the presentation, allowing developers to write a data engine once and then present this in an arbitrary number of ways in an applet. For example, once an engine to extract system performance state has been written, multiple plasmoids can present this information in different ways. A desktop plasmoid might have a large, detail-rich display, but the same data displayed on the panel might recognise its spatial constraints and display a simpler view.
Native Plasma applets can be implemented as containments, which are simply applets that can contain another applet. The panel is a containment, as is the desktop itself, and an applet contained within the panel can be dragged to the desktop or another panel, and vice versa, reforming and reflowing itself to fit its physical constraints.
This flexibility opens up, among other possibilities, the ability for scalable displays to enable a content-rich desktop on a PC or a display that's more suited to low-screen resolutions on an embedded device. KDE 4.1 plans to support OS X dashboard widgets, hinging on new features in a release of WebKit scheduled for early 2008.
Oxygen is the name chosen for the cohesive look and feel for the new KDE desktop. As well as creating beauty, the Oxygen team of artists is working with user interface guidelines to ensure that identification of elements is a priority. The result is a clean break from the previous KDE style, obviously inspired in part by already-existing artwork, but bringing it together with something fresh that is distinctly Oxygen's own. Oxygen also incorporates the system sound package, combining with the rest of the artwork to create something that is uniquely KDE.
With a team of three core icon designers, Oxygen relies on a set of strict style guidelines and an official colour palette to ensure a consistent result. The colours chosen are rich without being overpowering, and the icon design is modern and appealing.
An advantage of the new Oxygen icon theme is that it will be the first truly open KDE icon theme. The previous default for the long-running KDE 3 series, Crystal, never had its sources made available. The Oxygen team has been working exclusively in SVG, ensuring the set remains open.
The Oxygen style and window decoration is a large-scale departure from the Plastik style that became default in the late 3.x series. The muted pale gray and blue colours have made way for a brilliant off-white for both window decoration and controls. Green, orange and blue highlights are used sparingly with pleasing effect. The result looks extremely clean and modern, although such a large departure no doubt will draw some criticism. A wide range of colour schemes are available to suit almost every taste.
One minor concern about the new style is how much screen real estate it seems to use. We looked at KDE 4 on a Lenovo ThinkPad at 1400x1050 pixels, which seemed adequate for the task but by no means overgenerous. People still using 1024x768 or lower resolutions may struggle with the defaults.
A new wallpaper set has been collated, with the Oxygen artists acting as judges to select community submissions. The team chose 15 wallpapers, and the results are breathtaking. This kind of community involvement is unquestionably one of the strengths of the open-source development model.
Unfortunately, we were unable to preview the Oxygen sound theme properly—at the time of this writing, KDE 4 had not yet been released, and something about our sound card was causing the KDE sound system, Phonon, to crash.
Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
| Non-Linux FOSS: Seashore | May 10, 2013 |
| Trying to Tame the Tablet | May 08, 2013 |
- Using Salt Stack and Vagrant for Drupal Development
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- New Products
- New Products
- The Pari Package On Linux
- Dart: a New Web Programming Experience
- This is the easiest tutorial
2 hours 27 min ago - Ahh, the Koolaid.
8 hours 5 min ago - git-annex assistant
14 hours 5 min ago - direct cable connection
14 hours 28 min ago - Agreed on AirDroid. With my
14 hours 38 min ago - I just learned this
14 hours 42 min ago - enterprise
15 hours 12 min ago - not living upto the mobile revolution
18 hours 3 min ago - Deceptive Advertising and
18 hours 39 min ago - Let\'s declare that you have
18 hours 40 min ago








Comments
kde4 is very beta and very very bad
not pleased with kde4.
I don't like the look, I don't like the behavior.
I should never have upgraded to FC9.
What a mistake.
Too bad. I liked version 3.
#vocal singing lessons
kde4 is very beta and very very bad
not pleased with kde4.
I don't like the look, I don't like the behavior.
I should never have upgraded to FC9.
What a mistake.
Too bad. I liked version 3. How do I switch back?