Slashdot Mirror
The Road To KDE Frameworks 5 and Plasma 2
jrepin wrote in with a link to an article about the steps being taken toward a Qt5 based KDE 5 and Plasma Workspaces 2. From the article: "KDE's Next Generation user interfaces will run on top of Qt5. On Linux, they will run atop Wayland or Xorg as display server. The user interfaces move away from widget-based X11 rendering to OpenGL. Monolithic libraries are being split up, inter-dependencies removed, and portability and dependencies cut by stronger modularization. For users, this means higher quality graphics, more organic user interfaces and availability of applications on a wider range of devices. Developers will find an extensive archive of high-quality, libraries and solutions on top of Qt."
NX is already pretty much unusable with compositing DMs, do they have a solution for remote desktop connections?
Perhaps everyone is reading the article before commenting? I know...+5 Funny.
KDE 4.0 was missing a lot of expected 3.5 features, but a lot of the bad reputation it received were from terrible Kubuntu packages. The Kubuntu maintainers admitted they didn't understand the new build process or what they were doing. Canonical pushed it way too early and pushed crappy packages, but KDE took the blame. Early KDE builds on openSUSE, Arch, Fedora, etc. didn't have the same problems.
And honestly, I think only a year later (KDE 4.2) they had a great desktop for everyone.
The shift from KDE 3 to 4 (and Qt 3 to 4) meant a massive rewrite, and having to reinvent most of their core features.
KDE 5 sounds more like an evolution than revolution, so it should be smoother this time around.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
The summary essentially says "KDE is going to look better". Where are the screenshots?
KDE devs: Please do not screw up Kmail more than it already is. In fact, please put serious thought into restoring the good old filesystem-based folder database and just do away with that horrible Akonadi mistake that is dog slow, when it works at all. Running critical apps on top of a full blown database may look like a good idea on a Presenter slide, but in reality it is just cruel and unusual punishment.
I know this isn't strticly related to Qt5, but just try to keep it in mind ok? Thxbai.
When all you have is a hammer, every problem starts to look like a thumb.
A lot of classes were rewritten way back in the day when the licensing of Qt was under fire. Once those issues went away there really wasn't much point in continuing the duplication of effort. Bringing the two back together is long overdue. In the long run it could bring greater stability to KDE applications since more developers will be working on improving the same framework instead of two independent but close frameworks. This is good for both Qt and KDE.
I want this account deleted.
You're talking crap. KDE4 has managed wireless well for quite a long time. Not knowing this suggests you haven't used KDE4 in a long time and are just spouting some crap you once heard.
I love that people are arguing that KDE 4 is missing a "core feature" that was actually a third-party add-on for KDE 3, but at the same time argue that installing a plasmoid means the feature doesn't really exist.
KDE 4 was designed to be extendable, and supports multiple methods of easily installing plasmoids. Installing content from the internet into KDE 4 was a core underlying technology since 2008.
http://userbase.kde.org/Plasma/Installing_Plasmoids
http://newstuff.kde.org/
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.