Frameworks/Epics/Qt 5.0 Merging

From KDE Community Wiki
Revision as of 09:44, 27 December 2011 by Dfaure (talk | contribs) (add libinqt5 rules)

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 QCryptographicHash: QIODevice support, to replace KMD5 Sune
IN PROGRESS QMimeType David Faure [waiting for legal]
IN PROGRESS Contact John Layt to get an update on locales/datetime Mario Fux
IN PROGRESS Improved locales John Layt
IN PROGRESS Improved date/time John Layt
TO DO QCommandLineArguments Valentin Rusu; see qt5-feedback discussions <{{{3}}}>
TO DO KUrl/QUrl merge Thiago Macieira <{{{3}}}>
TO DO K/Q_GLOBAL_STATIC merge Thiago Macieira <{{{3}}}>
TO DO KAction/QAction merge Valentin Rusu <{{{3}}}>
TO DO KDebug features into QDebug ? <{{{3}}}>
TO DO KSsl*/QSsl* merge Richard Moore <{{{3}}}>
IN PROGRESS Refcounted quit Stephen Kelly
TO DO Organize a meeting to decide what's needed to move i18n forward Chusslove? Ossi? <{{{3}}}>

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