Whoops, re-sending to dev... On Tue, Mar 26, 2013 at 1:38 PM, Alan Alpert <[email protected]> wrote: > On Tue, Mar 26, 2013 at 12:32 AM, Stephen Kelly <[email protected]> > wrote: >> On Monday, March 25, 2013 18:19:57 Alan Alpert wrote: >>> More time to iterate is always welcomed. This may lead to a >>> source-incompatible change in Plasma Packages though, ideally we'd >>> only do that once with the existing incompatible change of KDE >>> Frameworks 5. Would that be using the 5.1 or 5.2 APIs? >> >> KDE Frameworks 5 will use the qt5.git dev branch until that has the features >> it needs. KDE won't release plasma+frameworks5 on top of Qt 5.1 because it >> doesn't have the required features. >> >> Whether Qt 5.2 will have all required features remains to be seen. The todo >> list is long: http://community.kde.org/Frameworks/Epics/Qt_5.1_Merging and >> even that list is only 'things needed in Qt before a release can be made'. >> The >> list of 'things to do in the KDE libraries before we can release' is also a >> long one. >> >> So, don't worry about release-timing relating to this issue. Whenever this >> feature reaches the qt5.git dev branch, the plasma developers can start using >> it in parallel development.
Oh good. I misread that page as "aiming to release on top of 5.1". >>> BlackBerry has run into performance issues reading from the >>> filesystem, but it's still not something to worry about until an API >>> is sorted out. >> >> Those problems were solved already, right? > In general, yes. But I'm still not happy with the costs of unnecessary file access in the QML engine so I've been working on reducing those (it's not a BlackBerry specific performance cost or fix, it's just one that's been noticed by BlackBerry apps). -- Alan Alpert _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
