Kate (the KDE Advanced Text Editor) is the well know, powerful text editor that ships by default in KDE, and has plenty of powerful features for both simple text editing as well as programmers. Some of the well-known functions that it offers include indentation, syntax highlighting for hundreds of programming languages, block-selection mode or check-spelling.
KWin5 will feature a new configuration module to control Desktop effects. KWin5 will be a part of the upcoming Plasma Next Workspace. The control module is rewritten with QtQuick controls.The focus of the control module will be on Desktop Effects.
The KDE community today released the second beta of Applications and Development Platform 4.13. With API, dependency and feature freezes in place, the focus is now on fixing bugs and further polishing. We kindly request your assistance with finding and fixing issues.
In the Plasma team, we’re working frantically towards the next release of the Plasma workspaces, code-named “Plasma Next”. With the architectural work well in place, we’ve been filling in missing bits and pieces in the past months, and are now really close to the intended feature set for the first stable release. A good time to give you an impression of what it’s looking like right now. Keep in mind that we’re talking Alpha software here, and that we still have almost three months to iron out problems. I’m sure you’ll be able to observe something broken, but also something new and shiny.
The last several months had become amazingly painful with Kontact, however. Frequently folders would lock up and the caches would fall out of sync; switching folders would take forever; loading mail content was also often painful. Restarting Kontact became a multi-day affair, and dropping Akonadi caches was becoming increasingly frequent. I chalked this up to running bleeding edge master, but my patience was growing thin. I filed bug reports, I started looking through the code to see where problems might be and I even considered what I could migrate to. (Nothing really comes close to Kontact, however ...)
So the other week I decided to take a drastic measure before going any further: I blew away all of the configuration and data files related to Kontact (including the individual apps such as KMail and KOrganizer) and Akonadi, keeping only my local maildir folders and started from scratch.
Some of your existing data will need to be migrated from the current Nepomuk backend to the new 'Baloo' backend. Running the nepomukbaloomigrator should take care of that. The old Nepomuk support is considered “legacy” (but it is still provided). The programs that have not yet been ported to the new architecture have Nepomuk integration disabled. One significant regression is file-activity linking, which will not work until KDE Applications and Platform 4.14. If you rely on this feature, we recommend not upgrading at this time. For the final release, distributions might choose to optionally have the old search (Nepomuk) available.
The primary goal of the conference was to encourage people to get involved with open source and to understand its power and its reach. We also wanted to help them get started by teaching them the basics and by getting them to know more about KDE. When the conference was over, it didn't matter how many lines of code anyone could understand or even actually write. If some people were convinced of the magic of open source and of KDE, and are now willing to be contributors to this noble cause even if only slightly, then the event accomplished its aim. Events, speakers and mentors like these add fuel to the fire inside. Students were inspired to reach out and experience the power of free and open source technology.
As my readers probably know there won’t be a combined release as the software compilation used to be. There are independent ongoing projects around the libraries (frameworks or KF5) the workspaces (Plasma Next) and the applications. These projects have independent release cycles and are not one product. I know, I know, many people will disagree and say that it’s still one. But if we go for this strong simplification both “will support Wayland” and “will not support Wayland” are true.
It’s Christmas time for KDE Software users, the team has just announced the first beta of the 4.13 versions of Applications and Development Platform. This release also marks a freeze on APIs, dependencies and features so the team will now focus on hunting down bugs and polish it further.
With these things in mind, I very quickly focused on two desktop managers that might provide the desired desktop: Xfce and Trinity. Since I prefer to use openSUSE as the underlying operating system and Xfce is one of the desktop manager options fully supported by openSUSE installations, Xfce was an obvious first choice for consideration. This article will consider the Xfce desktop manager from the perspective of a KDE4 user and it is addressed to all those KDE4 users who feel similarly frustrated with the development direction KDE4 has taken.