{"id":2851,"date":"2016-10-18T14:29:02","date_gmt":"2016-10-18T12:29:02","guid":{"rendered":"https:\/\/vizZzion.org\/blog\/?p=2851"},"modified":"2016-10-18T15:04:37","modified_gmt":"2016-10-18T13:04:37","slug":"plasmas-road-ahead","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2016\/10\/plasmas-road-ahead\/","title":{"rendered":"Plasma&#8217;s road ahead"},"content":{"rendered":"<p><figure id=\"attachment_2858\" aria-describedby=\"caption-attachment-2858\" style=\"width: 400px\" class=\"wp-caption alignright\"><a href=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/myplasma5.8.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/myplasma5.8-400x225.png\" alt=\"My Plasma Desktop in 2016\" width=\"400\" height=\"225\" class=\"size-medium wp-image-2858\" srcset=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/myplasma5.8-400x225.png 400w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/myplasma5.8-768x432.png 768w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/myplasma5.8-1024x576.png 1024w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/myplasma5.8-300x169.png 300w\" sizes=\"auto, (max-width: 400px) 100vw, 400px\" \/><\/a><figcaption id=\"caption-attachment-2858\" class=\"wp-caption-text\">My Plasma Desktop in 2016<\/figcaption><\/figure>On Monday, KDE&#8217;s Plasma team held its traditional kickoff meeting for the new development cycle. We took this opportunity to also look and plan ahead a bit further into the future. In what areas are we lacking, where do we want or need to improve? Where do we want to take Plasma in the next two years?<\/p>\n<p>Our general direction points towards professional use-cases. We want Plasma to be a solid tool, a reliable work-horse that gets out of the way, allowing to get the job done quickly and elegantly. We want it to be faster and of better quality than the competition.<\/p>\n<p>With these big words out there, let&#8217;s have a look at some specifics we talked about.<\/p>\n<h2>Release schedule until 2018<\/h2>\n<p>Our plan is to move from 4 to 3 yearly releases in 2017 and 2018, which we think strikes a nice balance between our pace of development, and stabilization periods around that. Our discussion of the release schedule resulted in the following plan:<\/p>\n<ul>\n<li>Plasma 5.9: 31 January 2017<\/li>\n<li>Plasma 5.10: May 2017<\/li>\n<li>Plasma 5.11: September 2017<\/li>\n<li>Plasma 5.12: December 2017<\/li>\n<li>Plasma 5.13: April 2018<\/li>\n<li>Plasma 5.14 LTS: August 2018<\/li>\n<\/ul>\n<p>A cautionary note, we can&#8217;t know if everything exactly plays out like this, as this schedule, to a degree depends on external factors, such as Qt&#8217;s release schedule. Here&#8217;s what we intend to do, it is really our &#8220;best guess&#8221;. Still, this aligns with Qt&#8217;s plans, who are also looking at an LTS release in summer 2018. So, what will these upcoming releases bring?<\/p>\n<figure id=\"attachment_2860\" aria-describedby=\"caption-attachment-2860\" style=\"width: 739px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.n31135.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.n31135-1024x625.png\" alt=\"Breeze Look and Feel\" width=\"739\" height=\"451\" class=\"size-large wp-image-2860\" srcset=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.n31135-1024x625.png 1024w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.n31135-400x244.png 400w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.n31135-768x469.png 768w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.n31135-300x183.png 300w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.n31135.png 1566w\" sizes=\"auto, (max-width: 739px) 100vw, 739px\" \/><\/a><figcaption id=\"caption-attachment-2860\" class=\"wp-caption-text\"><br \/>\n Breeze Look and Feel<\/figcaption><\/figure>\n<h2>UI and Theming<\/h2>\n<p>The Breeze icon theme will see further completion work\u00a0and refinements in its existing icons details. Icon usage over the whole UI will see more\u00a0streamlining work as well. We also plan to tweak the Breeze-themed scrollbars a bit, so watch out for changes in that area. A Breeze-themed Firefox theme is planned, as well as more refinement in the widget themes for Qt, GTK, etc.. We do not plan any radical changes in\u00a0the overall look and feel of our Breeze theme, but will further improve and evolve it, both in its light and dark flavors.<\/p>\n<h2>Feature back-log<\/h2>\n<p><figure id=\"attachment_2870\" aria-describedby=\"caption-attachment-2870\" style=\"width: 400px\" class=\"wp-caption alignright\"><a href=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.Jr4693.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.Jr4693-400x269.png\" alt=\"The menu button is a first sign of the global menu returning to Plasma\" width=\"400\" height=\"269\" class=\"size-medium wp-image-2870\" srcset=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.Jr4693-400x269.png 400w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.Jr4693-768x516.png 768w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.Jr4693-300x201.png 300w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.Jr4693.png 904w\" sizes=\"auto, (max-width: 400px) 100vw, 400px\" \/><\/a><figcaption id=\"caption-attachment-2870\" class=\"wp-caption-text\">The menu button is a first sign of the global menu returning to Plasma<\/figcaption><\/figure>One thing that many of our users are missing is support for a global menu similar to how MacOS displays application menus outside of the app&#8217;s window (for example at the top of the screen). We&#8217;re currently working on bringing this feature, which was well-supported in Plasma 4 back in Plasma 5, modernized and updated to current standards. This may land as soon as the upcoming 5.9 release, at least for X11.<\/p>\n<p>Better support for customizing the locale (the system which shows things like time, currencies, numbers in the way the user expects them) is on our radar as well. In this area, we lost some features due to the transition to Frameworks 5, or rather QLocale, away from kdelibs&#8217; custom, but sometimes incompatible locale handling classes.<\/p>\n<h2>Wayland<\/h2>\n<p>The next releases overall will bring further improvements to our Wayland session. Currently, Plasma&#8217;s KWin brings an almost feature-complete Wayland display server, which already works for many use-cases. It hasn&#8217;t seen the real-world testing it needs, and it is lacking certain features that our users expect from their X11 session, or new features which we want to offer to support modern hardware better.<br \/>\nWe plan to improve multi-screen rendering on Wayland and the input stack in areas such as relative pointers, pointer confinement, touchpad gestures, wacom tablet support, clipboard management (for example, Klipper). X11 dependencies in KWin will be further reduced with the goal to make it possible to start up KWin entirely without hard X11 dependencies.<br \/>\nOne new feature which we want to offer in our Wayland session is support for scaling the contents of each output individually, which allows users to use multiple displays with vastly varying pixel densities more seamlessly.<br \/>\nThere are also improvements planned around virtual desktops under Wayland, as well as their relation to Plasma&#8217;s Activities features. Output configuration as of now is also not complete, and needs more work in the coming months. Some features we plan will also need changes in QtWayland, so there&#8217;s some upstream bug-fixing needed, as well.<\/p>\n<p>One thing we&#8217;d like to see to improve our users&#8217; experience under Wayland is to have application developers test their apps under Wayland. It happens still a bit too often that an application ends up running into a code-path that makes assumptions that X11 is used as display server protocol. While we can run applications in backwards-compatible XWayland mode, applications can benefit from the better rendering quality under Wayland only when actually using the Wayland protocol. (This is mostly handled transparantly by Qt, but applications do their thing, so unless it&#8217;s tested, it will contain bugs.)<\/p>\n<h2>Mobile<\/h2>\n<p>Plasma&#8217;s Mobile flavor will be further stabilized, and its stack cleaned up, we are further reducing the stack&#8217;s footprint without losing important functionality. The recently-released <a href=\"https:\/\/dot.kde.org\/2016\/08\/10\/kdes-kirigami-ui-framework-gets-its-first-public-release\">Kirigami<\/a> framework, which allows developers to create convergent applications that work on both mobile and desktop form-factors, will be adjusted to use the new, more light-weight QtQuick Controls 2. This makes Kirigami a more attractive\u00a0technology to create powerful, yet lean applications that work across a number of mobile and desktop operating systems, such as Plasma Mobile, Android, iOS, and others.<\/p>\n<figure id=\"attachment_2863\" aria-describedby=\"caption-attachment-2863\" style=\"width: 739px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.X31135.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.X31135-1024x657.png\" alt=\"Plasma Discover\" width=\"739\" height=\"474\" class=\"size-large wp-image-2863\" srcset=\"https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.X31135-1024x657.png 1024w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.X31135-400x257.png 400w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.X31135-768x493.png 768w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.X31135-300x192.png 300w, https:\/\/vizZzion.org\/blog\/wp-content\/uploads\/2016\/10\/Spectacle.X31135.png 1576w\" sizes=\"auto, (max-width: 739px) 100vw, 739px\" \/><\/a><figcaption id=\"caption-attachment-2863\" class=\"wp-caption-text\">Discover, Plasma&#8217;s software center integrates online content from the KDE Store, its convergent user-interface is provided by the Kirigami framework<\/figcaption><\/figure>\n<h2>Online Services<\/h2>\n<p>Planned improvements in our integration of online services are dependency handling for assets installed from the store. This will allow us to support installation of meta-themes directly from the <a href=\"https:\/\/store.kde.org\/\">KDE Store<\/a>. We want to also improve our support for online data storage, prioritizing Free services, but also offer support for proprietary services, such as the GDrive support we recently added to Plasma&#8217;s feature-set.<\/p>\n<h2>Developer Recruitment<\/h2>\n<p>We want to further increase our contributor base. We plan to work towards an easier on-boarding experience, through better documentation, mentoring and communication in general. KDE is <a href=\"http:\/\/en.flossmanuals.net\/kde-guide\/the-kde-philosophy-and-community\/\">recruiting<\/a>, so if you are looking for a challenging and worthwhile way to work as part of a team, or on your individual project, join our ranks of developers, artists, sysadmins, translators, documentation writers, evangelists, media experts and free culture activists\u00a0and let us help each other.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>On Monday, KDE&#8217;s Plasma team held its traditional kickoff meeting for the new development cycle. We took this opportunity to also look and plan ahead a bit further into the future. In what areas are we lacking, where do we want or need to improve? Where do we want to take Plasma in the next&hellip; <a class=\"more-link\" href=\"https:\/\/vizZzion.org\/blog\/2016\/10\/plasmas-road-ahead\/\">Continue reading <span class=\"screen-reader-text\">Plasma&#8217;s road ahead<\/span> <span class=\"meta-nav\" aria-hidden=\"true\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14,26,22,29,25,28,32,35,20,24,38],"tags":[],"class_list":["post-2851","post","type-post","status-publish","format-standard","hentry","category-android","category-design","category-english","category-kde","category-linux","category-mobile","category-plasma","category-qt","category-solid","category-usability","category-wayland"],"_links":{"self":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/2851","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/comments?post=2851"}],"version-history":[{"count":21,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/2851\/revisions"}],"predecessor-version":[{"id":2876,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/2851\/revisions\/2876"}],"wp:attachment":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media?parent=2851"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/categories?post=2851"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/tags?post=2851"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}