[Development] [CI] reverse dependency testing

A while back, it was requested that the Qt Project CI should reject incoming changes to QtBase if they would cause compile or autotest failures in QtDeclarative. That is now implemented, which should reduce the risk of accidental source or behavior incompatible changes in qtbase. However, if you

Re: [Development] [Poll] Which direction should Qt Quick 2.x development take?

I also want to highlight the upcoming Qt Contributor Summit (June 21-23, Kalkscheune, Berlin, Germany), which is the perfect environment for Qt 5.1 discussion. (It's why we have the event in the first place.) More details here http://qt-project.org/groups/qt-contributors-summit-2012/wiki -- .m

Re: [Development] [Poll] Which direction should Qt Quick 2.x development take?

On Tue, 1 May 2012 06:50:55 ext Davet Jacques wrote: > Hi fellow Qt users, > > spread across various comment threads at the Qt developer forum, Qt Labs > blogs, and Qt mailing lists, there has recently been quite a bit of > discussion over the scope and priorities of Qt Quick, and whether or not >

Re: [Development] QDBus on Windows

Hi, On 30 Apr 2012 00:17:53 +0200, Andreas Holzammer wrote: > Installer can be found here: http://qt.gitorious.org/installer-framework > Packaging of Qt5 is public in QtRepotools > http://qt.gitorious.org/qt/qtrepotools In the subdirectory > release-tools. But Qt4 is not published, if I got the

Re: [Development] Deprecation warnings are enabled

On Monday 30 April 2012 21:34:45 lorn.pot...@nokia.com wrote: > On 01/05/2012, at 12:07 AM, ext Thiago Macieira wrote: > > On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote: > >> Just a notice to all devs: > >> > >> Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on Wed

Re: [Development] Deprecation warnings are enabled

On 01/05/2012, at 12:07 AM, ext Thiago Macieira wrote: > On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote: >> Just a notice to all devs: >> >> Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on Wednesday, all >> Qt modules have deprecation warnings enabled now. That

Re: [Development] Deprecation warnings are enabled

On segunda-feira, 30 de abril de 2012 22.36.41, Olivier Goffart wrote: > > I think most of them were related to qimage.h producing warnings (unless > > you were using gcc 4.6 or 4.7). > > Ah, that could be.. then those will dispear when we start to build without > deprecated function I suppose. Un

[Development] [Poll] Which direction should Qt Quick 2.x development take?

Hi fellow Qt users, spread across various comment threads at the Qt developer forum, Qt Labs blogs, and Qt mailing lists, there has recently been quite a bit of discussion over the scope and priorities of Qt Quick, and whether or not Nokia's (and the other Qt contributor's) roadmap, focus and d

[Development] Qt 5.0 beta and final timelines

Hi everybody, While I think it's very important to get Qt 5.0 out of the door as soon as possible, we should not release it without first getting it's quality to a very high standard. I think it has become rather clear that the original timeline of releasing Qt 5.0 by mid June is not doable anymo

Re: [Development] Deprecation warnings are enabled

On Monday 30 April 2012 19:55:25 lars.kn...@nokia.com wrote: > On 4/30/12 9:07 PM, "ext bradley.hug...@nokia.com" > > wrote: > >On Apr 30, 2012, at 8:50 PM, ext Olivier Goffart wrote: > >> On Monday 30 April 2012 17:57:46 bradley.hug...@nokia.com wrote: > >>> On Apr 30, 2012, at 7:19 PM, ext Thia

Re: [Development] Deprecation warnings are enabled

On segunda-feira, 30 de abril de 2012 19.55.25, lars.kn...@nokia.com wrote: > Ideally things such as the deprecated warnings should not be enabled until > someone went through things locally and made sure the amount of warnings > doesn't drown everything else. Let's please do this the next time. I

Re: [Development] Deprecation warnings are enabled

On segunda-feira, 30 de abril de 2012 19.00.31, bradley.hug...@nokia.com wrote: > But you're missing my point. I don't think anyone should be doing them. I > don't think now is the time to have a lot of "low-hanging fruit" changes > being pushed into to all the modules. See below. > The amount of

Re: [Development] Deprecation warnings are enabled

On 4/30/12 9:07 PM, "ext bradley.hug...@nokia.com" wrote: > >On Apr 30, 2012, at 8:50 PM, ext Olivier Goffart wrote: > >> On Monday 30 April 2012 17:57:46 bradley.hug...@nokia.com wrote: >>> On Apr 30, 2012, at 7:19 PM, ext Thiago Macieira wrote: On segunda-feira, 30 de abril de 2012 16.58.0

Re: [Development] Deprecation warnings are enabled

On Apr 30, 2012, at 8:50 PM, ext Olivier Goffart wrote: > On Monday 30 April 2012 17:57:46 bradley.hug...@nokia.com wrote: >> On Apr 30, 2012, at 7:19 PM, ext Thiago Macieira wrote: >>> On segunda-feira, 30 de abril de 2012 16.58.08, bradley.hug...@nokia.com >>> >>> wrote: Seriously? What a

Re: [Development] Deprecation warnings are enabled

On Apr 30, 2012, at 8:43 PM, ext Thiago Macieira wrote: > On segunda-feira, 30 de abril de 2012 17.57.46, bradley.hug...@nokia.com > wrote: >> When faced with two options, 1) fix deprecated warnings or 2) continue work >> to restore Qt 4 behavior in the platform plugins, I'm going to say we >> s

Re: [Development] Deprecation warnings are enabled

On Monday 30 April 2012 17:57:46 bradley.hug...@nokia.com wrote: > On Apr 30, 2012, at 7:19 PM, ext Thiago Macieira wrote: > > On segunda-feira, 30 de abril de 2012 16.58.08, bradley.hug...@nokia.com > > > > wrote: > >> Seriously? What about my comment (plea) to revert the change that enabled > >>

Re: [Development] Deprecation warnings are enabled

On segunda-feira, 30 de abril de 2012 17.57.46, bradley.hug...@nokia.com wrote: > When faced with two options, 1) fix deprecated warnings or 2) continue work > to restore Qt 4 behavior in the platform plugins, I'm going to say we > should be doing 2) and not do 1) at all (since there will be disrup

[Development] API review - proposed renaming of QAbstractSocket::PauseOnNotify to PauseOnSslErrors

https://codereview.qt-project.org/24905 Although we created an enum for pause modes to make 5.x binary compatible with 5.0, the enum value is not well named. In 5.1, we propose to add PauseOnProxyAuthentication to the enum. PauseOnNotify is not clear what it means, while PauseOnSslErrors is. Any

Re: [Development] Deprecation warnings are enabled

On Apr 30, 2012, at 7:19 PM, ext Thiago Macieira wrote: > On segunda-feira, 30 de abril de 2012 16.58.08, bradley.hug...@nokia.com > wrote: >> Seriously? What about my comment (plea) to revert the change that enabled >> these warnings? As I mentioned before (and others in my team), these >> warn

Re: [Development] Deprecation warnings are enabled

On segunda-feira, 30 de abril de 2012 16.58.08, bradley.hug...@nokia.com wrote: > Seriously? What about my comment (plea) to revert the change that enabled > these warnings? As I mentioned before (and others in my team), these > warnings are hurting more than helping, and our time is much better sp

Re: [Development] Deprecation warnings are enabled

On Apr 30, 2012, at 4:07 PM, ext Thiago Macieira wrote: > On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote: >> Just a notice to all devs: >> >> Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on Wednesday, all >> Qt modules have deprecation warnings enabled now. That

Re: [Development] QLogger questions and proposal

On Mon, Apr 30, 2012 at 1:27 AM, Lincoln Ramsay wrote: > On 04/25/2012 12:44 AM, ext Mike Zraly wrote: > >> On Mon, Apr 23, 2012 at 7:57 PM, Lincoln Ramsay >> > > >> wrote: >> I'm a little concerned about performance during shutdown if there are a >> large number

Re: [Development] When it coming about qbs plugin in Creator

On 30/04/2012 15:52, ext Loaden wrote: > It does not work. > Show me a error message: "Unknown property:qt.core.qtPath" When building it's still using the old property names. > Any commens? Yes. Be patient. Jörg ___ Development mailing list Developm

Re: [Development] Deprecation warnings are enabled

On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote: > You should not ignore them. You should use the replacement functions / > classes. One more thing: if you see a qMalloc, qRealloc or qFree in a public header, please move the code to a .cpp. Or at least leave a // ### FIXME so w

Re: [Development] Deprecation warnings are enabled

On 4/30/12 4:10 PM, "ext Giuseppe D'Angelo" wrote: >On 30 April 2012 15:07, Thiago Macieira wrote: >> On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote: >>> Just a notice to all devs: >>> >>> Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on >>>Wednesday, all >>> Qt

Re: [Development] Deprecation warnings are enabled

On 30 April 2012 15:07, Thiago Macieira wrote: > On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote: >> Just a notice to all devs: >> >> Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on Wednesday, all >> Qt modules have deprecation warnings enabled now. That means that

Re: [Development] Deprecation warnings are enabled

On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote: > Just a notice to all devs: > > Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on Wednesday, all > Qt modules have deprecation warnings enabled now. That means that when you > build your module, you'll get warnings abo

Re: [Development] D-Bus and (de-)marshalling of complex types (QDBusArgument)

On Thursday, April 26, 2012 12:19:14 Thiago Macieira wrote: > On quinta-feira, 26 de abril de 2012 11.49.02, Alberto Mardegan wrote: > > Hi all! > > > > The current QtDBus implementation automatically marshals only the > > > > basic D-Bus types, and puts all the complex types into a QDBusArgumen

Re: [Development] When it coming about qbs plugin in Creator

It does not work. Show me a error message: "Unknown property:qt.core.qtPath" > D:\qpSOFT\DEVx64>qbs config --list > local variables: > global variables: > defaults.platform: WinSDK7.1.7600.0.30514 > modules.qbs.platform: WinSDK7.1.7600.0.30514 > profile: qt4 > profiles.qt4.qt.core.path: D:\qpSOFT

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

On segunda-feira, 30 de abril de 2012 14.53.49, Thiago Macieira wrote: > On segunda-feira, 30 de abril de 2012 14.14.00, Kent Hansen wrote: > > Yes, it's late, but it's also one of the final nails in the const char > > *-based Q(Meta)Object introspection API coffin. > > [snip the rest] > > Needless

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

On 4/30/12 2:53 PM, "ext Thiago Macieira" wrote: >On segunda-feira, 30 de abril de 2012 14.14.00, Kent Hansen wrote: >> Yes, it's late, but it's also one of the final nails in the const char >> *-based Q(Meta)Object introspection API coffin. >[snip the rest] > >Needless to say, I support this cha

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

On segunda-feira, 30 de abril de 2012 14.14.00, Kent Hansen wrote: > Yes, it's late, but it's also one of the final nails in the const char > *-based Q(Meta)Object introspection API coffin. [snip the rest] Needless to say, I support this change, even though SIC. So here's my maintainer stamp of ap

[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] QtPrintSupport - Platform Support

On segunda-feira, 30 de abril de 2012 09.06.28, morten.sor...@nokia.com wrote: > Unfortunately, QCoreGraphicsPaintEngine needs to link against the Cocoa > platform plugin to use classes/methods in QCocoaAutoReleasePool and > QCocoaHelpers, but I can't figure out how to do that in qmake. QtGui and

Re: [Development] Proposing David Schulz as approver

On 20 Apr 2012, at 12:40, ext tobias.hun...@nokia.com wrote: > Hello Everybody! > > David has been working hard on the Qt Creator editor functionality for the > last months. For this reason I am proposing David Schulz as a approver in the > Qt project. Seconded. -- Eike Ziller Principal Sof

Re: [Development] QtPrintSupport - Platform Support

On Apr 28, 2012, at 5:38 PM, ext John Layt wrote: Well I've tried doing this and ended up moving QCocoaPrinterSupport, QQMacPrintEngine and QCoreGraphicPaintEngine all into the the printsupport plugin as they are all only used by QtPrintSupport, and as the plugin returns the native QPrintEngine a

Re: [Development] Nominating Jean Gressmann for Approver status

Hi, On Mon, Apr 30, 2012 at 10:56 AM, wrote: > Hi, > > I would like to nominate Jean Gressmann for Approver status in the Qt > Project. Jean has been working on QtLocation over the last few months, > contributing a good deal of code (a good deal of which has not being > especially romantic, l

Re: [Development] Nominating Jean Gressmann for Approver status

Seconded. -Alex W > -Original Message- > From: development-bounces+alex.wilson=nokia@qt-project.org > [mailto:development-bounces+alex.wilson=nokia@qt-project.org] On > Behalf Of Blasche Alex (Nokia-MP/Brisbane) > Sent: Monday, April 30, 2012 5:57 PM > To: development@qt-project.o

[Development] Nominating Jean Gressmann for Approver status

Hi, I would like to nominate Jean Gressmann for Approver status in the Qt Project. Jean has been working on QtLocation over the last few months, contributing a good deal of code (a good deal of which has not being especially romantic, lots of valuable documentation fixes and hacking away at aut

Re: [Development] Where is the QtLocation history?

On Fri, 27 Apr 2012 08:42:55 pm ext shane.kea...@accenture.com wrote: > Not sure if it's what you're looking for, but some old history is in > git://qt.gitorious.org/qt-mobility/qt-mobility.git in src/location. Not quite, the qt-mobility repository includes Qt Location source history which was im

Re: [Development] When it coming about qbs plugin in Creator

On 30/04/2012 03:44, ext Loaden wrote: > I am realy like the qbs, but now it's don't friendly for Creator. > So, when it coming as a plugin for Creator? As Orgad wrote, there's the work-in-progress branch wip/qbs. Status of the thing is: It can - load a qbs project and display the project tre