Frameworks/Epics/Qt 5.0 Merging

From KDE Community Wiki
Revision as of 14:34, 7 January 2013 by Dfaure (talk | contribs) (qtx11extras is 5.1 stuff, actually)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Merging features in Qt 5.0 epic

Quite some effort goes into Qt 5.0 in order to push into Qt some of the features which should be in Qt and not in KDE Frameworks. Usually because all Qt apps would benefit from them even outside the KDE world, and because this cuts dependencies between the KDE frameworks.

Important: The goal of this epic is to have all the features in Qt 5.0 before the feature freeze which is rumoured to happen "soon".

Target date: Ideally all of this should be done by the end of January 2012, to be sure not to miss the feature freeze.

Status Description Contact
DONE QStandardPaths David Faure
DONE QTemporaryFile (better defaults) David Faure
DONE QObject::findChildren(Qt::FindDirectChildrenOnly) David Faure
DONE QTemporaryDir David Faure
DONE QMimeData: export URLs as plain text too David Faure
DONE QCryptographicHash: QIODevice support, to replace KMD5 Sune
DONE Contact John Layt to get an update on locales/datetime Mario Fux
DONE Refcounted quit Stephen Kelly, change 10408
DONE QMimeType David Faure, change 15585
DONE KUrl/QUrl merge David Faure and Thiago Macieira (QUrl)
DONE KDebug features into QDebug Started by Kai Koehne (Nokia) in change 13433, then Wolfgang Beck implemented category logging (13226), and an addon for the API (see QTBUG-19536). Missing API in Qt itself -> 5.1
DONE Native event filtering in QCoreApplication David Faure, change 29260
DONE QSignalSpy::wait (replaces kWaitForSignal) David Faure, change 30799
DONE Add app display name to window titles David Faure, change 42627

Once a class is ready to be merged into Qt, it can also be added to KDE frameworks in libinqt5/src. When we port KDE frameworks to Qt 5, we will get rid of libinqt5 and we'll use qt master directly.

If the addition to Qt is a new method rather than a new class, then an intermediate solution has to be found (e.g. QDir::removeRecursive is temporarily QTemporaryDir::removeRecursive in libinqt5, so that we know we use a Qt method for this, and we can easily port to the real Qt5 method when the time comes).