Re: [Development] qtfeedback and qtdocgallery: status?

dback and qtdocgallery: status? On Tuesday 22 March 2016 09:58:48 Hausmann Simon wrote: > As the modules are not part of any release of Qt and unmaintained, I don't > think they need fixing. C'mon — FTBFS without the possibility to submit a fix? -- Marc Mutz <marc.m...@kdab.com> | Senior S

Re: [Development] qtfeedback and qtdocgallery: status?

As the modules are not part of any release of Qt and unmaintained, I don't think they need fixing. Simon From: m...@kdab.com <m...@kdab.com> on behalf of Marc Mutz <marc.m...@kdab.com> Sent: Tuesday, March 22, 2016 9:37 To: Hausm

Re: [Development] http://testresults.qt.io/ci/status/ stale?

Not implemented feature. That site is a mirror of the internal system and we do not mirror running integrations currently. Simon Original Message From: Marc Mutz Sent: Tuesday, March 22, 2016 08:50 To: development@qt-project.org Subject: Re: [Development] http://testresults.qt.io/ci/status/

Re: [Development] Qt Coding Guidelines

I agree with Rich. This isn't documentation our users are facing. We don't need to extract from cpp files or use a particular style sheet. +1 for Kai's initiative. Simon From: Richard Moore Sent: Wednesday, March 16, 2016 22:55 To: Knoll Lars Cc: development@qt-project.org Subject: Re:

Re: [Development] QtQuick Call for Maintainer

+alot :) Simon From: Development on behalf of Eskil Abrahamsen Blomfeldt Sent: Thursday, March 10, 2016 10:43 To:

Re: [Development] QNX broken on 5.7

No worries :). The fact that you didn't see a proper configure error message suggests that the follow up patch to verify the qnx installation didn't make it or is buggy. Hmm. Simon Original Message From: Rafael Roquetto Sent: Tuesday, March 8, 2016 19:48 To: Hausmann Simon Cc: development

Re: [Development] QNX broken on 5.7

Hi, When building Qt 5.7 for QNX a special patch is applied in the CI that fixes the Dinkumware headers. You were CCed when this was discussed (Subject was "‎QNX and Dinkumware support for constexpr and nullptr"). Simon Original Message From: Rafael Roquetto Sent: Tuesday, March 8, 2016

Re: [Development] change log creation tool (was: Re: Qt 5.6.0 missing change files)

@qt-project.org> on behalf of Thiago Macieira <thiago.macie...@intel.com> Sent: Saturday, February 27, 2016 0:58 To: development@qt-project.org Subject: Re: [Development] change log creation tool (was: Re: Qt 5.6.0 missing change files) On sexta-feira, 26 de fevereiro de 2016 19:06:06

Re: [Development] change log creation tool (was: Re: Qt 5.6.0 missing change files)

Sent: Friday, February 26, 2016 17:59 To: development@qt-project.org Subject: Re: [Development] change log creation tool (was: Re: Qt 5.6.0 missing change files) How is this different from the tool that already exists? On sexta-feira, 26 de fevereiro de 2016 12:34:45 PST Hausmann Simon wrote

[Development] change log creation tool (was: Re: Qt 5.6.0 missing change files)

Hi, To simplify the creation of the change files I have written a small tool that facilitates this job. It's written in golang and you get install it by simply running go get code.qt.io/qt/qtqa.git/src/createchangelog The binary will be placed in $GOPATH/bin. (If you are not familiar

Re: [Development] GCC-built Qt 5.6 can't be used with Clang

Hi, Hmm, change ‎https://codereview.qt-project.org/#/c/147846/ was supposed to fix this issue. ‎The subject of the email refers to 5.6 but in the body you say that you are building the dev branch. If it is the latter, could it be that the fix hasn't hit dev yet? Simon Original Message

Re: [Development] Scalable UIs in QtQuick (take 2)

..@gmail.com>> wrote: > > 2016-02-18 12:50 GMT+02:00 Hausmann Simon > <simon.hausm...@theqtcompany.com<mailto:simon.hausm...@theqtcompany.com>>: >> (1) In order to make it really easy to scale "logical" pixels without having >> to introduce your own

Re: [Development] Scalable UIs in QtQuick (take 2)

From: Ирина Flora <ritt...@gmail.com> Sent: Thursday, February 18, 2016 11:57 To: Hausmann Simon Cc: development@qt-project.org Subject: Re: [Development] Scalable UIs in QtQuick (take 2) I like it! Some questions though: * Does (2) include coverage for cases like 5cm ? * Could w

[Development] Scalable UIs in QtQuick (take 2)

Hi, A little while ago Lars and I proposed to introduce physical units in the QML language for use in QtQuick. The idea was to make it easier to write user interfaces that adapt to different display resolutions by "pinning" your UI to physical dimensions. For example you could say Image {

Re: [Development] Modify QLibraryInfo to support any default location of qt.conf

You're right, the can is open right now. Apple is working on closing that can under our feet (see the DYLD_* variable unsetting upon exec in 10.11). I wouldn't be surprised if that trend continues elsewhere :) Simon From: Development

Re: [Development] RTSP H264 under Windows

Judging from responses on the internet like https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/4ac87f5f-b8c5-471a-a424-55c0fff04eac/using-the-media-foundation-sdk-to-parse-rtsp-streams?forum=mediafoundationdevelopment I have the impression that the Media Foundation in Windows does

Re: [Development] Setting up test server for QtNetwork tests

Regarding the server that is used for Qt 5.6 and onwards: It is an exact clone of the virtual machine that ran in Jenkins with no changes to the services, but it is in a different virtual network segment. The virtual segment is the same as the virtual machines that run the tests, and that has

Re: [Development] Setting up test server for QtNetwork tests

Hi, In principle that manual is still correct. There was work going on towards automating the setup for everyone through the use of a vagrant template that would call puppet, etc. do to the installation. I believe that was still part of a work-in-progress branch in qtbase, but it hasn't hit

Re: [Development] Status of QtMultimedia module

Hi, I can't response to the aspect of which bugs are considered and how code reviews happen, but regarding your statement of the development being stalled: I'm counting 37 landed changes in January 2016 until today, that's more than a change per day. I can also see changes going in regularly

Re: [Development] qtdeclarative-5.6.0-beta build failure on rhel6

Ok, I had another look. I don't think find_if is new in C++11: ‎http://en.cppreference.com/w/cpp/algorithm/find It seems find_if_not is, but not find_if. So I think what we see here is‎ simply a compiler bug perhaps? Thanks to Marco it seems that we have a workaround:

Re: [Development] tvOS port

Awesome work :) Simon From: Development on behalf of Mike Krus Sent: Monday, January 25, 2016 21:06 To: Qt Development Group Subject: [Development] tvOS port Hi during the xmas break, I took

Re: [Development] Question about QCoreApplicationData::*_libpaths

Hi, Could you elaborate where you see copy on write causing writes to shared cache lines? Are you concerned about the shared cache line for the reference count? For reading MESI allows for shared cache lines and for hyper threads the shared l1 data cache mode favors sharing and thus CoW. What

Re: [Development] What kind of airplane we want to build?

Hi, I think answering the question about the kind of airplane to build is closely tied to another question that may be worthwhile asking. I think it's worthwhile because I'm convinced that answers diverge greatly depending on who you ask. Why are we trying to build an airplane? Or

Re: [Development] V4 porting

Hi, Moth is the portable interpreter that will be used instead of the just-in-time compiler if your platform doesn't support it. It should be chosen automatically for you according to the #ifdefs in qv4global_p.h. So if you have qtbase compiling, then qml should also work. If you want things

Re: [Development] V4 porting

Hi, Registers that are native to the processor are saved on the regular stack. Simon From: Dmitriy - Sent: Thursday, December 24, 2015 14:11 To: Hausmann Simon Cc: development@qt-project.org Subject: Re: [Development] V4 porting One more question: qt-5.5.1/qtdeclarative/src/qml/jit

Re: [Development] V4 porting

into an intermediate representation (codegen), optimizations in that IR and finally register allocation and native code generation or byte code generation. I'm afraid that I don't have a road map for your porting efforts. Simon From: Dmitriy - Sent: Thursday, December 24, 2015 12:42 To: Hausmann Simon

Re: [Development] wec2013 build fails with qt 5.6 beta in dbus.

We ran into similar issues in a few places and the established workaround is a carefully placed #undef interface. Would you be able to tell us where the conflict happened or maybe even make a patch? (see qtnetwork for a similar #undef) Simon From: Gunnar Roth Sent: Monday, December 21, 2015

Re: [Development] Review request for ArrayBuffer+WebSocket/XHR (a.k.a Introducing protobuf-qml)

Hi, I've started reviewing your series of patches. Excellent work! Thank you for contributing your changes back. I also think that protobuf bindings would make a lot of sense to have in Qt itself. Is there any chance that you could make it to the next Qt contributor summit and we have a

Re: [Development] qtdeclarative 5.6 CI status

The crisis is over and resolved - happy staging :) Simon Original Message From: Hausmann Simon Sent: Monday, December 14, 2015 15:34 To: development@qt-project.org Subject: [Development] qtdeclarative 5.6 CI status Hi, I can see how people keep trying to integrate changes

[Development] qtdeclarative 5.6 CI status

Hi, I can see how people keep trying to integrate changes into qtdeclarative's 5.6 branch. Until https://codereview.qt-project.org/#/c/143824/ lands, all those attempts of integrating changes are going to fail, unfortunately :) Simon ___

[Development] Fw: Change in qt/qt5[dev]: Updated submodules.

015 07:22 To: Qi Liang Cc: Hausmann Simon; Qt Sanity Bot; Nowacki Jedrzej; Gladhorn Frederik; Abrahamsen-Blomfeldt Eskil; Denis Shienkov; Kokko Antti Subject: Change in qt/qt5[dev]: Updated submodules. Qt CI Bot has posted comments on this change. Change subject: Updated subm

Re: [Development] glib's and Qt's RuntimeLocation [OS X]

Hi, I think the chances of a Qt application depending on glib on Mac OS X are extremely slim, given that glib is not part of the default system installation. I think the much more common case of a Qt application on Mac OS X is to just use Qt and the system APIs without any third-party library

Re: [Development] Nominating Pasi Keränen for Approver status

+1 Simon From: Development on behalf of Frederik Gladhorn Sent: Monday, November 23, 2015 12:46 To: development@qt-project.org Subject: [Development] Nominating Pasi Keränen for

[Development] PSA: 5.6 branch integrations

Hi, Due to a hiccup in the qtbase build system any integrations targetting the 5.6 branch in modules other than qtbase that depend directly or indirectly on qtdeclarative are going to fail until further notice. Examples of affected modules include qttools, qtwebengine, etc. I suggest to hold

Re: [Development] PSA: 5.6 branch integrations

Hi, Thanks to Ossi's analysis and efforts this is fixed now. Simon Original Message From: Hausmann Simon Sent: Thursday, November 19, 2015 09:15 To: development@qt-project.org Subject: [Development] PSA: 5.6 branch integrations Hi, Due to a hiccup in the qtbase build system any

Re: [Development] New qt5.6 beta snapshot available

Hi, Namespaced builds are only tested on Linux IIRC, not os x. Similarly static builds happen for ios, where the plugin loading code is probably not used. Simon Original Message From: Tim Blechmann Sent: Tuesday, November 17, 2015 05:24 To: development@qt-project.org Subject: Re:

Re: [Development] RFD: plugins vs QStringLiterals

And moc data is affected in a similar way. I continue to be in favor of (3) Simon Original Message From: Thiago Macieira Sent: Friday, November 6, 2015 00:44 To: development@qt-project.org Subject: [Development] RFD: plugins vs QStringLiterals Proposal: force QStringLiteral uses to always

Re: [Development] Stepping down as Windows Embedded Compact port maintainer

+1x2 Simon Original Message From: Thiago Macieira Sent: Friday, October 23, 2015 22:15 To: development@qt-project.org Subject: Re: [Development] Stepping down as Windows Embedded Compact port maintainer On Friday 23 October 2015 11:49:00 Knoll Lars wrote: > > > >Big +1 from my side,

Re: [Development] Nominating Allan Jensen as maintainer for Qt WebEngine

+1 Simon From: development-bounces+simon.hausmann=theqtcompany@qt-project.org on behalf of Koehne Kai Sent: Thursday, October 15, 2015 11:25 To:

Re: [Development] New Qt Modules

I think code that isn't specific to the automotive industry such as as the dbus integration should be integrated into existing modules unless there is a good reason otherwise. Just my two cents, Simon From: Viironen Kalle Sent: Tuesday, October 13, 2015 09:35 To: development@qt-project.org

Re: [Development] QML import versions

Hi, I agree that something "new" needs to be put on the table in order to solve this. And "this" expands unfortunately to a few issues at the same time. I think that it would be a mistake of "import QtQuick" - without any version tag - would always import the latest available version on

Re: [Development] How to speed up QML for KDE5 without QML compiler

Hi, I think there's a trade-off to be made with regards source (url) vs. sourceComponent. If the component your loader is trying to load is small, then you're better off using sourceComponent. While the parser and the type compiler is "warm" it should take little time to do the one-time work

Re: [Development] Requesting New Repository - QtZeroConf

Hi, Given that mdns uses an unprivileged port, it seems like to me it should be possible for just about any process to send and receive mdns queries. Which means that any app could participate in the mdns groups by itself if it wanted. The primary advantage that I can see with re-using a

Re: [Development] Documentation proposal: Remove recommended reading list of 20-year-old books

I think that there is a b‎ig difference between it being easy enough to find reading material and us - the project - making specific recommendations for material that we think is of particularly high quality and perhaps also relevance. The latter adds real value to our documentation. I think

Re: [Development] 5.5 CI having problems on tst_qmimedatabase-xml

Right, in 5.5 any stale state on the file system is likely to survive. In dev (new ci) that problem is gone. Simon Original Message From: Thiago Macieira Sent: Thursday, August 6, 2015 18:14 To: development@qt-project.org Subject: Re: [Development] 5.5 CI having problems on

Re: [Development] [Releasing] HEADS-UP: Qt 5.6 feature freeze and branching coming

Hi, We can fix this. Do we just need to install recent openssl headers (no libs) and provide them wi‎th configure? Simon From: Richard Moore Sent: Monday, August 3, 2015 14:04 To: Heikkinen Jani Cc: development@qt-project.org; releas...@qt-project.org Subject: Re: [Releasing] [Development]

Re: [Development] HEADS-UP: Qt 5.6 feature freeze and branching coming

Hi, Qt5.git updates in dev are not working yet. We are however working on it full time, trying to get it done asap. Simon From: Heikkinen Jani Sent: Monday, August 3, 2015 12:55 To: development@qt-project.org Cc: releas...@qt-project.org Subject: [Development] HEADS-UP: Qt 5.6 feature freeze

[Development] ios build issues

scratch for every build (per module). ‎Any help greatly appreciated! Simon Original Message From: Qt CI Bot (Code Review) gerrit-nore...@qt-project.org Sent: Monday, July 13, 2015 18:47 To: Hermann Ulf Cc: Qt Sanity Bot; Hausmann Simon Subject: Change in qt/qtdeclarative[dev]: With -no-qml

Re: [Development] The dark side of QtMultimedia - strikes back

Hi, Could you elaborate how omxplayer uses gstreamer? I only see openmax il usage, but perhaps I am missing something. Thanks, Simon From: Massimo Callegari Sent: Saturday, July 4, 2015 22:19 To: development@qt-project.org Reply To: Massimo Callegari Cc: thiago.macie...@intel.com Subject:

Re: [Development] Fwd: (QTBUG-46655) qt5base: font license files missing

Make that two votes :) Simon Original Message From: Thiago Macieira Sent: Tuesday, June 16, 2015 22:40 To: development@qt-project.org Subject: Re: [Development] Fwd: (QTBUG-46655) qt5base: font license files missing On Tuesday 16 June 2015 12:28:51 Paul Olav Tvete wrote: There is

Re: [Development] QVariantMap - QML

Hi, This is a result of QVariant being a value type. If you make a copy and modify it, then the original remains as-is. The call to setContextProperty creates a copy. If you want explicitly shared data between the JavaScript environment and C++ then I would recommend using a JavaScript object

Re: [Development] Avoid overloading of 'error'

Hi, Perhaps my German is rusty, but I find on error translates well to German with bei/beim: Beim Auftreten eines Fehlers Simon Original Message From: Konrad Rosenbaum Sent: Saturday, June 13, 2015 12:54 To: development@qt-project.org Subject: Re: [Development] Avoid overloading of

Re: [Development] Avoid overloading of 'error'

it's better to stick to error() than to have some QML types have onError and some have onFailure. Simon From: Alan Alpert 4163654...@gmail.com Sent: Wednesday, June 10, 2015 18:59 To: Hausmann Simon Cc: Thiago Macieira; development@qt-project.org Subject

Re: [Development] Specifying module dependencies

: Wednesday, June 10, 2015 22:21 To: development@qt-project.org Subject: Re: [Development] Specifying module dependencies On Wednesday 10 June 2015 19:33:37 Hausmann Simon wrote: Any particular reason against json, btw? Qmake can read it out of the box, as opposed to .ini. So the only other option I

Re: [Development] Specifying module dependencies

Hi, Why do we need to pin anything beyond the regular git submodules handling of qt5.git (where the information is in the tree object)? In think we should have a configuration file in each module listing required and optional dependencies. Qt.pro can interpret that file and so can the CI

Re: [Development] Avoid overloading of 'error'

Hi, I think renaming the getter to lastError is nice! I however do like error as signal name and it looks good in qml as onError:... Simon Original Message From: Thiago Macieira Sent: Wednesday, June 10, 2015 16:35 To: development@qt-project.org Subject: Re: [Development] Avoid overloading

Re: [Development] New Module for Serial Buses

Good point :) I was under the assumption that the concepts are too different, but if they aren't then maybe a joint module would make sense. Simon Original Message From: Thiago Macieira Sent: Tuesday, May 26, 2015 17:06 To: development@qt-project.org Subject: Re: [Development] New Module for

[Development] Binary compatibility for qtestlib

‎Hi, Lately development of testlib picked up again and I've been wondering: the api consists of a fair amount of macros that call internal functions. It would be convenient to change the signature of those while maintaining source compatibility, however it would naturally break the ABI. On

Re: [Development] Binary compatibility for qtestlib

Okay, thanks - that sounds good to me. The change in particular that I was thinking of is ‎https://codereview.qt-project.org/#/c/112690/ It could be done without breaking BC but it's easier if we can :) Simon From: Jason McDonald Sent: Wednesday, May 20, 2015 13:27 To: Hausmann Simon Cc

Re: [Development] Future of Qt Quick 1 in Qt 5

Hi, Compilation wise I agree, it's low effort. But the situation is different in Jira IMO. Simon Original Message From: Thiago Macieira Sent: Friday, May 8, 2015 17:37 To: development@qt-project.org Subject: Re: [Development] Future of Qt Quick 1 in Qt 5 On Friday 08 May 2015 14:39:38

Re: [Development] Future of Qt Quick 1 in Qt 5

Hi, If the public API would allow you to implement what the folks at KDAB did at http://www.kdab.com/creating-pdf-qtquick-2-scene-slideviewer/ ‎, would that help your use case? Simon Original Message From: André Somers Sent: Friday, May 8, 2015 14:45 To: development@qt-project.org Subject:

Re: [Development] RFC: QtQuick. Custom keys support proposal.

Hi, Let me see if I understand this correctly: 1. The Keys attached object supports _any_ key through the generic pressed and released signals and the event parameter that comes with them. 2. There are a couple of convenience signals for commonly used keys. You would like to add private API to

Re: [Development] Qt 4.8.7 release candidate available

IMO this isn't a Qt bug, I commented on Jira. I suspect another app isn't implementing the protocol directly, but if we really want to protect ourselves then we should probably ditch the entire session management code from Qt 4 (it's gone in Qt 5, too :) Simon Original Message From: Matthew

Re: [Development] Qt 4.8.7 release candidate available

Sure, with the removal I only meant the xsm implementation :) Simon Original Message From: Samuel Gaist Sent: Thursday, April 30, 2015 23:36 To: Hausmann Simon Cc: Matthew Woehlke; development@qt-project.org; releas...@qt-project.org Subject: Re: [Development] Qt 4.8.7 release candidate

Re: [Development] Are SiCs through #include cleanups considered acceptable?

I think that would be a good compromise. Simon Original Message From: Olivier Goffart Sent: Friday, April 10, 2015 15:56 To: development@qt-project.org Cc: Hausmann Simon Subject: Re: [Development] Are SiCs through #include cleanups considered acceptable? On Friday 10. April 2015 13:38:55

Re: [Development] Why are qtbase integrations taking so long?

Hi, I believe what we are seeing is caused by instability in the network that connects the Jenkins service with the Jenkins slave machines. Occasionally network connectivity between the slaves and the master is lost, causing the running build as a whole to abort - all other still running

Re: [Development] bug: qmake ignores CMAKE_CC and CMAKE_CXX while building Qt 5.3.2???

‎Hi, Should bootstrap really use the mkspec compiler? I'm not sure that's always the right thing. Bootstrap should just use _any_ compiler. What is the underlying problem that you are trying to solve? Simon Original Message From: René J.V. Bertin Sent: Sunday, March 22, 2015 21:24 To:

Re: [Development] bug: qmake ignores CMAKE_CC and CMAKE_CXX while building Qt 5.3.2???

2015 20:33:53 Hausmann Simon wrote: Should bootstrap really use the mkspec compiler? Yes, that's what the -platform option is for. The target compiler is specified by -xplatform. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center

Re: [Development] Code Coverage Statistics for QtBase

Why can they be ignored? When the users run Qt applications that code is executed, so coverage is important IMO. However if the added code is from build tools (Code generators) then maybe it's not so critical, as long as the generated code is covered. That said, the results look incomplete to

Re: [Development] Proposed syntax change for pragmas and imports in QtQuick .js files

Hi, We need a syntax that allows determining the dependencies unambiguously from the AST. ES 6 module import syntax allows for that, Qt.import doesn't unfortunately. Simon From: Chris Adams Sent: Tuesday, February 17, 2015 09:31 To: Mike Verdone Cc: development@qt-project.org Subject: Re:

Re: [Development] Proposed syntax change for pragmas and imports in QtQuick .js files

Hi, In principle I think that's a very good direction. However .pragma singleton does not exist for .js files :). Qt.import as a substitute for .pragma import would be great. In an ideal world we'd support es6 modules. Simon Original Message From: Mike Verdone Sent: Monday, February 16,

Re: [Development] why is QJSEngine not modifying metaObject

To: development@qt-project.org Subject: Re: [Development] why is QJSEngine not modifying metaObject On Wednesday 11 February 2015 07:11:26 Hausmann Simon wrote: Hi, The short answer to your question is that the meta object system isn't really designed for this. In theory this could

Re: [Development] QtDeclarative CI failures on Windows

Hi, Friedemann made a fix: ‎https://codereview.qt-project.org/#/c/105750/ Simon Original Message From: Robin Burchell Sent: Tuesday, February 10, 2015 21:15 To: development@qt-project.org Subject: [Development] QtDeclarative CI failures on Windows Can someone with Windows please take a look

Re: [Development] why is QJSEngine not modifying metaObject

Hi, The short answer to your question is that the meta object system isn't really designed for this. In theory this could be implemented but it would come at a high cost for something that rarely happens. The qml engine supports this, but in qml this happens at type compilation time, not fully

Re: [Development] Upgrading the sources to C++11 keywords (Q_NULLPTR, etc.)

I suppose that it is absolutely unlikely that we are going to find a consensus on what is purely an aesthetic issue. I for one am entirely with André and I do not like UPPERCASE macros in my face unless I can avoid them. It's aesthetics and I suppose there is little that will change that. As

Re: [Development] Deprecating modules with 5.5

Hi, Functionality wise, what type of class do you wrap with QScriptClass? Simon Original Message From: Jaroslaw Staniek Sent: Tuesday, February 3, 2015 09:36 To: Knoll Lars Cc: development@qt-project.org Subject: Re: [Development] Deprecating modules with 5.5 On 3 February 2015 at 09:29,

Re: [Development] CI broken

Thanks Ismo, Tony, Ossi and all the people behind the scenes to get things up and running again! Simon From: Sarajärvi Tony Sent: Tuesday, January 27, 2015 20:41 To: development@qt-project.org Subject: Re: [Development] CI broken I think I got everything up and running again. At least

Re: [Development] Qt 5.4.0 final packages to be tested

Yeah, that's an unfortunate bug that slipped in. It is documented as a known issue and tracked in ‎QTBUG-43205 Simon Original Message From: Uwe Rathmann Sent: Wednesday, December 10, 2014 12:14 To: development@qt-project.org Subject: Re: [Development] Qt 5.4.0 final packages to be tested

Re: [Development] Clarification needed for Qt Script's future over QJSEngine/Value

Hi, You are right, we need to add a few more features to QJSEngine. I'm not so much in favor of the default prototype for meta type api anymore, as it promotes the creation of slow conversion code I think. If you peek at my gerrit dashboard then you can see that I'm about 80% done with a

Re: [Development] CI broken again

Great analysis - thanks guys for fixing this! Simon Original Message From: Morten Johan Sørvig Sent: Monday, October 20, 2014 21:06 To: Qt Development Group Subject: Re: [Development] CI broken again On 20 Oct 2014, at 15:04, Saether Jan-Arve jan-arve.saet...@theqtcompany.com wrote:

[Development] Fw: Change in qt/qtdeclarative[5.4]: Fix QQmlExpression/QQmlScriptString/QQmlBinding crashes

‎Hi, Does anyone know what's up with the build on windows ce? I've seen this failure in various integrations in the past days. Simon Original Message From: Qt Continuous Integration System (Code Review) gerrit-nore...@qt-project.org Sent: Wednesday, October 8, 2014 13:19 To: Hausmann Simon

Re: [Development] [QML] Singletons are deleted before the other objects

Hi, In gener‎al I agree with Chris. However I'm a little puzzled that this is happening. If you take a look at the QQmlEngine destructor you can see that singletons are deleted last. So I'm wondering what is happening in your app Bogdan. Can you create a minimal test case? Thanks, Simon Fra:

Re: [Development] Qt WebChannel 5.5 roadmap: WebEngine, QtWebView

I'm pretty sure that all the native webview APIs allow for at least runJavascript(string), so injection may also be an easier option. Simon Opprinnelig melding Fra: Jocelyn Turcotte Sendt: 16:45 onsdag 27. august 2014 Til: Milian Wolff Kopi: Development Emne: Re: [Development] Qt WebChannel

Re: [Development] Fwd: Change in qt/qtbase[5.4]: Add the QStorageInfo class

Yay :) Simon Opprinnelig melding Fra: Thiago Macieira Sendt: 21:43 onsdag 13. august 2014 Til: development@qt-project.org Emne: [Development] Fwd: Change in qt/qtbase[5.4]: Add the QStorageInfo class It merged. -- Forwarded Message -- Subject: Change in qt/qtbase[5.4]:

Re: [Development] HEADS UP: Qt 5.4 feature freeze - is frozen now

Hi, I sincerely hope that the class name will be reconsidered, given how generic and therefore ambiguous the term volume is. Please consider making it more specific by adding Storage or something else to the name and avoid that people guess wrongly and avoid people finding this class when they

Re: [Development] QWebChannel setTimeout

I think setTimeout would be a good function to add to qml's Javascript environment, as imperative js api next to the timer element. That said, the risk is high that people use it to drive animations or work around other things. Anyway, patches welcome :) Simon Opprinnelig melding Fra:

Re: [Development] QWebChannel setTimeout

Let me ask the other way around: is there a special reason why you're including qwebchannel.js in a qml application? :) Simon Opprinnelig melding Fra: Bernd Lamecker Sendt: 19:41 fredag 4. juli 2014 Til: development@qt-project.org Emne: [Development] QWebChannel setTimeout Hi, is there a

Re: [Development] QtQuick QtCS Sessions

The done is referring to the fact that a binding to qsTr(...) does not result in the creation of a Javascript binding but is treated directly by the engine as translation. just like the jira report indicates, support for dynamic re-evaluation of such bindings is not implemented yet (and was

Re: [Development] qt5.git integration failed in stable

I suspect one of these three changes in qtbase: ‎Revert Fixed duplicate QMoveEvent generated for each QWidget::move call Fix selection by dragging after double click in QWidgetTextControl. QPlatformClipboard::emitChanged(): Do not emit signals when closing down. Do those ring a bell for

Re: [Development] [HEADS UP] new branching scheme: 5.3 branches created, stable deprecated

Whether or not next is a better name than dev is your opinion, it isn't necessarily a fact. I for one like dev and find it a name better than next. We could run a poll and see what name comes out and change to that. But is it really worth the effort and disruption?‎ I'm not convinced that it

Re: [Development] split() and replace() methods SEGFAULT

You're right, Gatis ran into the same issue. Seems arm jit specific, he made a nice js only test case. (see 39289) Simon Opprinnelig melding Fra: Zoltán Balogh Sendt: 07:50 tirsdag 27. mai 2014 Til: development@qt-project.org Emne: [Development] split() and replace() methods SEGFAULT Hi,

Re: [Development] qt-opensource-windows-x86-msvc2012_opengl-5.3.0-RC: libegl missing

Hmm I don't think the _opengl variant is supposed to contain libegl (angle) - I think only the angle variant is supposed to. Simon Opprinnelig melding Fra: Helmut Mülner Sendt: 09:39 mandag 12. mai 2014 Til: development@qt-project.org Emne: [Development]

Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

Oops you're right, it's there. Thanks ‎:) Simon Opprinnelig melding Fra: Alan Alpert Sendt: 23:32 onsdag 30. april 2014 Til: Hausmann Simon Kopi: Hartmann Thomas; development@qt-project.org Emne: Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future

Re: [Development] No SSL on iOS ?

Unfortunately dlopen is not possible :( Simon Opprinnelig melding Fra: Thiago Macieira Sendt: 18:14 mandag 28. april 2014 Til: development@qt-project.org Emne: Re: [Development] No SSL on iOS ? Em seg 28 abr 2014, às 09:44:49, Nichols Andy escreveu: The packaged (binary) versions of iOS do

Re: [Development] Question about Qt's future

Hmm, but why don't you use Qml like that then? The language doesn't force you to use inline js code, does it? A lot of the work that has gone into the engine lately also enables this to work better and reduce the use of JS. For example bindings that just consist of a qsTr don't actually end up

Re: [Development] Qt binaries with inlined functions

Hi, Isn't this also how msvc behaves by default? Then perhaps it would make sense to build with those flags by default with gcc for consistency. I wonder what the overhead in size is. Either way I think this should not be specific to qt-project.org binaries. Simon Fra: Dimitar Dobrev Sendt:

Re: [Development] Question about Qt's future

Hi Michael, In response to your email I have two questions: 1) As your email is addressed to the open source community working on Qt itself, who are you referring to with they? 2) You are saying that you want to be sure. What kind of assurance are you looking for? Simon Opprinnelig

Re: [Development] Python required to build Qt from source packages

packages Em sex 28 fev 2014, às 18:30:24, Hausmann Simon escreveu: Note that this is not a new dependency but has been there since Qt 5.0.0 (when v8 required python) Still. Can we please commit the file to the repository or generate it at packaging time? Opprinnelig melding Fra: Thiago

Re: [Development] qt5.git integration broken again :(

lørdag 15. mars 2014 Til: Hausmann Simon Kopi: Gladhorn Frederik; Heikkinen Jani; development@qt-project.org Emne: Re: [Development] qt5.git integration broken again :( I apologize about the breakage of the build :'( ___ Development mailing list

Re: [Development] Python required to build Qt from source packages

Note that this is not a new dependency but has been there since Qt 5.0.0 (when v8 required python) Simon Opprinnelig melding Fra: Thiago Macieira Sendt: 18:04 fredag 28. februar 2014 Til: development@qt-project.org Emne: [Development] Python required to build Qt from source packages We

  1   2   >