KDE Releases Frameworks 5 Tech Preview 51
KDE Community writes "The KDE Community is proud to announce a Tech Preview of KDE Frameworks 5. Frameworks 5 is the result of almost three years of work to plan, modularize, review and port the set of libraries previously known as KDElibs or KDE Platform 4 into a set of Qt Addons with well-defined dependencies and abilities, ready for Qt 5. This gives the Qt ecosystem a powerful set of drop-in libraries providing additional functionality for a wide variety of tasks and platforms, based on over 15 years of KDE experience in building applications. Today, all the Frameworks are available in Tech Preview mode; a final release is planned for the first half of 2014. Some Tech Preview addons (notably KArchive and Threadweaver) are more mature than others at this time."
Check out that dependency graph.
Re:Backwardness of KDE continues (Score:5, Informative)
"True innovation would be to provide a script-based approach to most of the GUI stuff, e.g. nodejs/browser API .. and then provide native code layer"
We started working on exactly that ~5 years ago and the result is QML2 and Plasma (two separate things, but they work wonderfully together). As the node.js project founder said when he saw QML for the first time: "Wow, it's HTML5 done right."
So KDE is truly innovative, you're just too uninformed to have known and ~5 years too late to the suggestion table. (I'm not entirely sure how the /. smarminess works, but I gave it my best try with that last sentence .. did I succeed? ;)
Re:Backwardness of KDE continues (Score:5, Informative)
Re:The real summary about KDE Framework 5... (Score:4, Informative)
... is the idea of load as few as possible libraries to run a KDE application in a non KDE environment.
No, that's not it. The purpose is to break useful functionality out of KDE and make it available to QT developers in general without requiring KDE itself. The benefit to KDE is, it prepares the ground for migration to QT 5, cleans things up, and enables the possibility of contributions to the framework components by non-KDE developers. Or in other words, whatever is good for QT it good for KDE.