contador web Saltar al contenido

The tracks that will guide KDE development in the coming years

It is difficult to happen that many days without post something about the KDE project. Fortunately for all of us, this is a very large and consolidated project, used by many, and in constant development. Recently the team posted on its official website which are the three main objectives on which to base project development in the coming years.

Having set goals is essential to maintaining a steady and well-targeted development. Work simply doesn't work if it's not organized, and focused. The areas where the KDE community would like to improve, and the news they would like to implement are many, but the staff and resources are limited. Therefore, the best way to keep the project evolving is to focus efforts on specific points, and focus on improving only a few things at a time.

If you are a newcomer to the Linux world, and KDE, you may not know that the KDE project goes far beyond its graphical interface, Plasma Desktop. The KDE community maintains hundreds of different projects, ranging from simple panel time and date plugins and widgets, to audio conversion programs, video editing, and all the complexity of Plasma Desktop.

Keeping all this work going in an organized way is certainly not easy, which is why over the next two years all the team work will be done with the following goals in mind:

KDE Apps

As mentioned earlier, the KDE project maintains a wide range of applications. One of the main goals for developers in the coming years to improve the look and feel of these apps. The KDE team pointed out in the official post that the design of many of these apps will be reworked to make them a more organized interface, which should make using these apps easier for new users.

Perhaps these changes have improved an aspect that has been criticized by users for a long time, that the fact that KDE applications display an exaggerated amount of options and functions, making things a little, or rather confusing, for users. It will also work on the appearance and behavior of applications that use tabs, burger menus, and sidebars.

Another goal is to eliminate, or at least decrease application fragmentation. That is, if the project currently has two or more multimedia players, it will only have one. This way developers can focus their efforts on just one or two software in each segment, depending on the need, and thus make them better and more complete.

But of course it won't just be visual enhancements, certainly we can also expect improvements under the cap. Such as packaging improvements, bug fixes and performance tweaks.

Speaking of KDE Apps, did you know that one of the best existing tools for connecting your smartphone to your computer is maintained by the KDE project? If you don't know KDE Connect, you should!

Wayland Support

Enhancing Wayland support is one of the key goals of the KDE community. According to the team, Wayland perfectly fits the design philosophy of creating a functional, light and beautiful product, always with the latest technologies and offering the best possible performance.

If you don't know what the hell Wayland, the video below is sure to give you a light.

Although a priority, developers say that the full implementation of Wayland is not something that happens overnight. Many things can simply be modified and made compatible to work with the X.org replacement, but others need to be rewritten from scratch. Which takes a lot of work and resources.

In this regard, efforts will be focused primarily on making Kwin, Plasma, and KDE apps compatible, but the KDE community also intends to collaborate directly with the development of Wayland itself as much as possible.

Consistency

It's about creating new apps with similar graphical interfaces that are part of the whole. As well as modifying the layout of existing application interfaces so that everyone looks coherent. Something very similar to what, for example, the GNOME project, and the Elementary OS team has been doing for a long time.

The idea is to make systems using KDE Plasma and KDE apps easier to use. By learning to use a software, the user already knows, or at least has a good understanding of how others work. Since they will all share the same design patterns, thus making them easier to learn and master.

In addition, maintaining a visual standard among KDE applications also strengthens the brand. Since applications can be recognized as coming from the KDE project with just a glance.

However, these changes bring benefits beyond visual or UX Design. Visual applications following the same pattern reduce the number of redundant codes and designs, so maintaining them becomes easier and less labor intensive. For example, if a save button was previously designed for each application, now the design of a single save button can be used in several different applications.

This will also reduce the difficulty and workload of developing new software. Since many lines of code and interface designs can be reused from one application to another.

It's been a while since I've only used GNOME Shell as my main interface, but I've always been, and I'm still an admirer of the KDE project. Incidentally, that is the good side of this world of open source software, there are so many great products that we are not usually able to use them all.

By the way, if you are a KDE user and like to leave the system with your face. We have a really complete video that will get you very well on track when it comes to customizing KDE Plasma.

Do you like the KDE ecosystem? What do you think about the orientations the project is taking for its future development? Tell us your opinion in the comments.

Do you like Linux and technology? Got a question or problem you can't solve? Come join our community in the Diolinux Plus!

This is all folks!

________________________________________________________________________________________

See an error or would you like to add any suggestions to this article? Collaborate, click here.