Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
KDE Programming

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.
This discussion has been archived. No new comments can be posted.

KDE Releases Frameworks 5 Tech Preview

Comments Filter:
  • by ustolemyname ( 1301665 ) on Wednesday January 08, 2014 @01:51PM (#45899443)

    That dependency graph is beautiful.

    I wish gcc had a --fno-circular-dependencies flag to force that on a codebase (much like go does in the language spec).

    • That dependency graph is beautiful.

      Agreed, I'm now kompletely konvinced of their eventual success.

    • Unfortunately Go doesn't have any modular/plugin system (other than source.) The FFI is better now with C++, and I'm sure we'll get dynamic loading eventually. The whole KDE framework is predicated on shared libs, services and plugins. I like Go but making a platform like KDE in Go would be impossible.

  • ... is the idea of load as few as possible libraries to run a KDE application in a non KDE environment.
    • by Tough Love ( 215404 ) on Wednesday January 08, 2014 @04:25PM (#45901027)

      ... 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.

  • by hduff ( 570443 ) <hoytduff.gmail@com> on Wednesday January 08, 2014 @03:17PM (#45900431) Homepage Journal

    What a Kool Desktop Environment.

    • I admire the attempt at consistency with the K everywhere. Well, sort of. The commentary below doesn't apply to necessarily to this specific release or grouping of work. I also concede that it's time spent and in some cases money. Further, I admit that many will actually like it.

      I'm probably not one of them. I order regular coffee and have it black. I don't get the Frappe/Crape or whatever stuff gets put in.

      But really, I'm getting older. I don't want to learn someone's new paradigm for user interface

Adding manpower to a late software project makes it later. -- F. Brooks, "The Mythical Man-Month"