Frameworks/Epics/Qt 5.0 Merging

< Frameworks‎ | Epics
Revision as of 11:12, 20 January 2012 by Dfaure (talk | contribs) (updates)
Jump to: navigation, search

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
DONE Contact John Layt to get an update on locales/datetime Mario Fux
IN PROGRESS QMimeType David Faure [in qt playground now, waiting for Wolf-Michael to review 13154, and for Thiago/Lars to do an API review]
IN PROGRESS Improved locales John Layt (see development list)
IN PROGRESS Improved date/time John Layt
IN PROGRESS KUrl/QUrl merge Thiago Macieira (see development list)
IN PROGRESS K/Q_GLOBAL_STATIC merge Thiago Macieira (see development list)
IN PROGRESS KDebug features into QDebug Started by Kai Koehne (Nokia) in change 13433, with input from Thiago and David
TO DO QCommandLineArguments Laszlo Papp; see qt5-feedback discussions <{{{3}}}>
TO DO KAction/QAction merge Valentin Rusu <{{{3}}}>
TO DO KSsl*/QSsl* merge Richard Moore <{{{3}}}>
TO DO Refcounted quit <{{{3}}}>
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).


Content is available under Creative Commons License SA 4.0 unless otherwise noted.