[Development] Changelog for 5.0 (Was: [Releasing] Content freeze for Qt 4.8.3 approaching)

Hi Akseli, Den 03. aug. 2012 15:10, skrev ext Salovaara Akseli: > > Hi all, > > It has been great to notice that Qt 4.8 branch is active and has > already well over 200 commits since Qt 4.8.2 release. > > Therefore it is suitable time to start creating Qt 4.8.3 release, as > discussed earlier.

Re: [Development] QtScript vs Qml/QJsEngine ?

Hi, Den 30. mai 2012 15:23, skrev ext Diego Iastrubni: > On Wed, May 30, 2012 at 4:11 PM, Olivier Goffart > wrote: > > On Saturday 26 May 2012 12:51:23 Stephen Kelly wrote: > > Hi, > > > > There is a discussion on a kde list touching on whether there is a

Re: [Development] QtScript vs Qml/QJsEngine ?

Hi Stephen, Den 26. mai 2012 12:51, skrev ext Stephen Kelly: > Hi, > > There is a discussion on a kde list touching on whether there is a replacement > for QtScript in Qt 5. > > http://thread.gmane.org/gmane.comp.kde.devel.kwrite/32993/focus=75079 > > Is the QJSEngine the start of public API provi

Re: [Development] On QML, ownership, QObject-trees and QSharedPointer

Den 25. mai 2012 02:35, skrev ext christopher.ad...@nokia.com: > Hi, > >>> In QtQuick 2.0 (ie, Qt 5.0), we are thinking about using property var >>> more often in the implementation (eg, of qobject-derived-type >>> properties) to avoid some of those edge-cases, and providing more >>> consistent (an

Re: [Development] Nominating Peter Varga for approver status

Hi, Den 23. mai 2012 09:02, skrev ext Simon Hausmann: > Hi, > > I would like to nominate Peter for approver status. > > As part of the team in the University of Szeged he has completed the past few > rebases of V8 in the qtjsbackend module, a task that is anything but easy, > with a fast moving up

Re: [Development] Qt5 API change coming up: QObject::connectNotify(const char *) --> connectNotify(QMetaMethod)

Hi, The const char *-based API is now gone (https://codereview.qt-project.org/#change,24426). Thanks to all who helped get the qt5 submodule porting changes through. Best regards, Kent Den 30. april 2012 14:14, skrev ext Kent Hansen: > Hi all, > Quick links: https://bugreports.qt-proje

Re: [Development] Notice: QtDeclarative compatibility module about to be removed

Hi, It's removed now. Kent Den 11. mai 2012 09:50, skrev ext Kent Hansen: > Hi, > See https://codereview.qt-project.org/#change,25891 > > In short, "QT += declarative" and the QtDeclarative headers/classnames > will no longer work (i.e., code that use them won'

[Development] Notice: QtDeclarative compatibility module about to be removed

Hi, See https://codereview.qt-project.org/#change,25891 In short, "QT += declarative" and the QtDeclarative headers/classnames will no longer work (i.e., code that use them won't compile). I went through the qt5.git submodules and ported the last stuff (hopefully) over to the QtQml names. Once

Re: [Development] QtV8: Order of arguments on Runtime::kResolvePossiblyDirectEval inconsistent

Hi Holger, Den 08. mai 2012 23:04, skrev ext Holger Hans Peter Freyther: > Hi, > > I am looking into why QtV8 stopped working for MIPS (the obvious candidate is > that there is lithium support now). While doing this I noted that in > FullCodeGenerator::EmitResolvePossiblyDirectEval the following i

[Development] Qt5 API change coming up: QObject::connectNotify(const char *) --> connectNotify(QMetaMethod)

Hi all, Quick links: https://bugreports.qt-project.org/browse/QTBUG-25541 and https://codereview.qt-project.org/#change,24282 (TL;DR; skip down to "IMPACT ON EXISTING connectNotify() REIMPLEMENTATIONS") Yes, it's late, but it's also one of the final nails in the const char *-based Q(Meta)Object

Re: [Development] api_changes merged back to master

Den 19. april 2012 13:44, skrev ext Thiago Macieira: > On quinta-feira, 19 de abril de 2012 12.42.18, Kent Hansen wrote: >> Hi, >> qtpim is merged. Thank you. >> >> qtsystems also got merged. >> >> That leaves only qtmultimedia, I believe. This is fai

Re: [Development] api_changes merged back to master

Hi, qtpim is merged. Thank you. qtsystems also got merged. That leaves only qtmultimedia, I believe. This is failing: FAIL! : tst_QMediaPlaylist::loadM3uFile() Compared values are not the same Actual (playlist.media(4).canonicalUrl()): /testdir/testfile Expected (QUrl(QLatin

Re: [Development] api_changes merged back to master

qtdeclarative/api_changes got merged, and now several others after that. qtpim, qtsensors and qtsystems still remaining (merge attempts are all in progress). Best regards, Kent Den 18. april 2012 00:29, skrev ext Donald Carr: > yetch, and again, sorry Kent > > Were I but a beautiful woman, I

Re: [Development] The qtbase CI should run the qtdeclarative tests

Den 19. mars 2012 10:32, skrev ext Thiago Macieira: > On segunda-feira, 19 de março de 2012 08.01.41, lars.kn...@nokia.com wrote: >>> Yes, in some ways I feel this is adding complexity to the test setup to >>> work around a "false simplicity" in our source code setup. We claim >>> that Qt is modul

Re: [Development] The qtbase CI should run the qtdeclarative tests

Den 19. mars 2012 10:29, skrev ext Rohan McGovern: > Knoll Lars (Nokia-MP/Oslo) said: >> On 3/19/12 2:11 AM, "ext Rohan McGovern" wrote: >> >>> marius.storm-ol...@nokia.com said: While it's not normal to do this type of dependency "lock" for upwards dependencies, i think in this case we

Re: [Development] Staging of qtdeclarative changes has been blocked while we try to unpin the qtbase SHA1

Den 13. mars 2012 12:08, skrev ext Kent Hansen: > > It's difficult to know which type of changes can break stuff in other > modules, but things like > > - QtCore/Gui event/timer handling > - Gui text/font changes > - Network changes (declarative uses networking ext

Re: [Development] Staging of qtdeclarative changes has been blocked while we try to unpin the qtbase SHA1

Den 12. mars 2012 23:45, skrev ext Rohan McGovern: > Richard Moore said: >> On 12 March 2012 17:56, wrote: >>> Besides flaky tests, we also have the general/recurring problem of changes >>> going into qtbase that break qtdeclarative (and possibly/likely other >>> modules). While I realize it's t

[Development] Staging of qtdeclarative changes has been blocked while we try to unpin the qtbase SHA1

Hi, qtdeclarative needs to be adapted to some recent changes in qtbase. While we try to get that done (http://codereview.qt-project.org/#change,18941), staging of unrelated changes to qtdeclarative has been blocked. Best regards, Kent ___ Development

Re: [Development] Nominating Girish Ramakrishnan for Approver status

Yes, please! Welcome back, Girish! Kent Den 06. mars 2012 10:06, skrev ext lars.kn...@nokia.com: > Hi, > > I'd like to nominate Girish for Approver status. He's been around Qt for a > pretty long time, working for Trolltech a couple of years ago, then having > his own consultancy company doing Q

[Development] Changing the return type of QMetaMethod::signature()

Hi, As part of http://codereview.qt-project.org/#change,14763 (new meta-object data format) it would be good to change the return type of QMetaMethod::signature() from const char * to QByteArray. In the new meta-data format, the raw, 0-terminated signature string is no longer stored; the signat

Re: [Development] Changing qreal to a float

Den 15. feb. 2012 08:38, skrev ext gunnar.sle...@nokia.com: > For some time we have wanted to unify the behavior of qreal on desktop and > embedded. Currently, qreal is defined to be double on desktop and to a float > on embedded. > > The reasons for unifying are: > > - Using "double" is pure w

Re: [Development] Feature freeze and Alpha

Yep. https://bugreports.qt-project.org/browse/QTBUG-24154 Kent Den 08. feb. 2012 13:40, skrev Knoll Lars (Nokia-MP/Oslo): > Ok, this one makes sense to finish IMO. > > Can you please add a Jira task for it, and make it a subtask for 20885? > > Lars > > On 2/8/12 1:20

Re: [Development] Feature freeze and Alpha

Den 05. feb. 2012 15:12, skrev ext lars.kn...@nokia.com: > Hi everybody, [...] > Is there anything that I have now forgotten that really *must* be in 5.0 > (i.e. it really can't be done in a BC/SC way for Qt 5.1)? If you have such > an item, please speak up, otherwise I'll consider the above except

Re: [Development] Configuration changes for QStateMachine

Den 02. feb. 2012 14:39, skrev ext Caio Marcelo de Oliveira Filho: > Hello, > > I didn't have time to provide a patch this week, but I would like to > get this in Qt 5.0 if possible -- I'm willing to write the necessary > changes and tests for it. > > QTBUG-9380: It would be useful if QStateMachine

Re: [Development] Status of ActiveQt module?

Den 01. feb. 2012 12:48, skrev ext Robin Burchell: > 2012/2/1 Jedrzej Nowacki: >> Yes, and by updating QMetaObjectBuilder we will update data generated by >> ActiveQt. ActiveQt would use the newest meta object version (faster&& >> tested). > As (I think) was raised on Gerrit - this requires that so

Re: [Development] Status of ActiveQt module?

Den 01. feb. 2012 09:47, skrev ext Olivier Goffart: > Facts: > 1) QMetaObjectBuilder is private, its API may still change from minor version > to minor version That's fine. It's still better (lower maintenance) than having home-grown / incompatible generators floating around, IMO. > 2) Qt mainta

[Development] QByteArrayRef

Hi, It would be useful to have a QByteArrayRef class, similar to QStringRef -- a thin wrapper that doesn't copy the data. Did anyone implement it already? If not, I can take a stab at it. Kent ___ Development mailing list Development@qt-project.org htt

[Development] Moving .ico image format support out of qtbase?

Hi, The .ico plugin was originally a Qt Solution, but in Qt 4.4 it was made part of Qt because QtWebKit needed it. Does QtWebKit still need it? Does anyone else need it? In any case, would it be OK to move it to the new qtimageformats module (where MNG and TIFF were moved already)? Then QtWebKit

[Development] Status of ActiveQt module?

Hi, Does anyone care about the ActiveQt module for Qt5? A problem with this module is that it doesn't have any autotests. I can run some on the examples, but I don't really know what they're supposed to do, or how to use them to exercise relevant codepaths. The main reason I'm asking is because

Re: [Development] Suggestion for new CI: "early warning" for qt5.git

Den 30. jan. 2012 06:03, skrev Rohan McGovern: > > As Joao mentioned, this relates to "a dry run of the CI" feature. > I think that we need a method of requesting that some test procedure is > run over your change in gerrit, without also testing some set of everyone > else's changes at the same tim

Re: [Development] Suggestion for new CI: "early warning" for qt5.git

Den 27. jan. 2012 14:07, skrev ext Olivier Goffart: > On Friday 27 January 2012 09:09:46 Kent Hansen wrote: > [...] >> If there is no quick fix, the last resort is to "pin" one or >> more of the dependencies' to a particular SHA1 (e.g. from the qt5.git >> s

Re: [Development] Suggestion for new CI: "early warning" for qt5.git

Den 27. jan. 2012 09:20, skrev Alan Alpert: > On Fri, 27 Jan 2012 18:09:46 ext Kent Hansen wrote: >> Hi, >> Sometimes there are changes to qtbase that the author and/or reviewers >> strongly suspect will break one or more modules on top of it (e.g. in >> qt5.git). For e

[Development] Suggestion for new CI: "early warning" for qt5.git

Hi, Sometimes there are changes to qtbase that the author and/or reviewers strongly suspect will break one or more modules on top of it (e.g. in qt5.git). For example, source-incompatible changes (removing QEventLoop::DeferredDeletion), or changes to the meta-type/QObject internals (which qtdec

Re: [Development] V8's location

Den 03. jan. 2012 22:07, skrev ext lars.kn...@nokia.com: > On 1/3/12 5:45 PM, "ext Oswald Buddenhagen" > wrote: > >> On Tue, Jan 03, 2012 at 01:45:27PM -0200, ext Thiago Macieira wrote: >>> Configure already sets a "default" mkspec symlink that matches the >>> target >>> mkspec. Making it also crea

Re: [Development] V8's location

Den 03. jan. 2012 15:51, skrev ext Kent Hansen: > > I created http://code.google.com/p/v8/issues/detail?id=1885 for the icc > fix (note that I'm not allowed to submit patches :( ). Make sure to vote > for it! ;) I'll import your patch into our tree for the time being. The

Re: [Development] V8's location

Den 30. des. 2011 15:06, skrev ext Thiago Macieira: > On Monday, 12 de December de 2011 19.34.21, Thiago Macieira wrote: >> On Monday, 12 de December de 2011 18.03.53, aaron.kenn...@nokia.com wrote: $ git reset --hard d28b6a024826aaa48a8b3e69c096d01c91aff2c9 Checking out files: 100% (894/

Re: [Development] V8's location

Den 01. jan. 2012 20:59, skrev ext simon.hausm...@nokia.com: > Whoever is going to do the work may first have to add support for host builds > in modules outside qtbase, in order to support v8 snapshots. > > Simon > Hmm, I was getting ready to create a JIRA task ("Add support for host builds in

Re: [Development] QtQuick becomes a separate module

Den 02. des. 2011 16:27, skrev ext Kent Hansen: > > By the way, the suggestion on the table was to abuse fixqt4headers to > also support updating these "Qt 4.99" includes > (QtDeclarative/qquickitem.h => QtQuick/qquickitem.h, et al). Done; if you're using QQuickVie

Re: [Development] QtQuick becomes a separate module

Den 02. des. 2011 16:11, skrev ext Kent Hansen: > The change went through, and qtdeclarative is open for staging again. Just to clear any confusion: Existing Qt5/QtQuick1-based projects are not affected by this change. I.e. if you're using QDeclarativeView and friends, no "QT

Re: [Development] QtQuick becomes a separate module

Den 02. des. 2011 16:13, skrev ext Charley Bay: > > Den 02. des. 2011 09:33, skrev ext Kent Hansen: > > > Hi, > > See https://bugreports.qt.nokia.com/browse/QTBUG-22889 > > > > Once http://codereview.qt-project.org/#change,9948 goes through CI,

Re: [Development] QtQuick becomes a separate module

Den 02. des. 2011 09:59, skrev Kent Hansen: > > Den 02. des. 2011 09:33, skrev ext Kent Hansen: >> Hi, >> See https://bugreports.qt.nokia.com/browse/QTBUG-22889 >> >> Once http://codereview.qt-project.org/#change,9948 goes through CI, > > Since the commit is s

Re: [Development] QtQuick becomes a separate module

Den 02. des. 2011 09:33, skrev ext Kent Hansen: > Hi, > See https://bugreports.qt.nokia.com/browse/QTBUG-22889 > > Once http://codereview.qt-project.org/#change,9948 goes through CI, Since the commit is so huge, there's a high likelyhood of conflicts and failing tests when co

[Development] QtQuick becomes a separate module

Hi, See https://bugreports.qt.nokia.com/browse/QTBUG-22889 Once http://codereview.qt-project.org/#change,9948 goes through CI, QtQuick will be a separate module (AKA library). This is where all the QtQuick (2.0) types will live, and QtQuick-specific C++ APIs, like QQuickItem and scenegraph. Th

Re: [Development] V8 updated in qtbase.git

One thing we just remembered is that we want to have v8 snapshot support when cross-compiling. So we'll have a mkv8snapshot tool that must run on the host. How can that be achieved if we move v8 out of qtbase? Currently makefiles for host tool are handled in configure, see this line: *

[Development] V8 updated in qtbase.git

Hi, bcd16f9453e543ba819385d87bd7061a4caeb325 bumps the sha1 for the V8 submodule, and introduces some build changes to src/v8. You'll need to do "git submodule update" to be able to build libQtV8 again. Thiago, I missed the previous discussion on V8's location. Since everyone seems to agree tha