Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

KDE Programming

KDE Releases Frameworks 5 Tech Preview 51

Posted by Unknown Lamer
from the when-kde-and-qt-become-one dept.
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 K. S. Kyosuke (729550) on Wednesday January 08, 2014 @02:20PM (#45899801)

    To make an analogy, cars didn't exactly put railways out of business. Good luck trying to convince companies like Autodesk to port their humongous applications for specialists to radically different environments just because a /. AC wants them to.

    True innovation would be to provide a script-based approach to most of the GUI stuff, e.g. nodejs/browser API - essentially drop the entire QT/GTK mess (you had your chance, and failed), and replace it with WebKit and JavaScript engine, and then provide native code layer to provide an interface for computational demanding stuff.

    Also, did you notice that that Qt QML and Qt Quick are already heading in the direction you've just outlined?

You are lost in the Swamps of Despair.