Language Selection

English French German Italian Portuguese Spanish

The future of KDE: Wayland, Qt 5, uniform Plasma shell

Filed under
KDE
Software

The road to Plasma Workspaces 2 has been laid out as the Plasma developers recently met in Nuremberg, Germany, to discuss their open issues around future developments. A new version of the KDE desktop will be based on version 5 of the KDE platform and on Qt 5, writes KDE developer Sebastian Kügler. It will be designed to run on X11 as well as on Wayland. With Wayland, KWin will be used as the compositor.

The developers plan to integrate the various device-specific desktop interfaces (Plasma Desktop, Plasma Netbook, Plasma Active for touch devices, Plasma Mediacenter) into a workspace shell that can switch workspaces and behaviours via "shell packages". Packages will be available dynamically for selection at runtime, for example allowing the Plasma workspace to transform from a touch-optimised user interface into a classic desktop when a keyboard and mouse are connected to a tablet.

more here or 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