Re: [Development] Nominating Pasi Petäjäjärvi for Approver status

Congrats! _ From: Blasche Alexander > Sent: Tuesday, December 15, 2015 3:21 AM Subject: Re: [Development] Nominating Pasi Petäjäjärvi for Approver status To:

Re: [Development] Nominating Samuli Pippo for Approver status

+1! _ From: Meadows Louis > Sent: Wednesday, December 2, 2015 2:01 PM Subject: Re: [Development] Nominating Samuli Pippo for Approver status To:

Re: [Development] Nominating Pier Luigi Fiorini (plfiorini) as an Approver

On 15 Jul 2015, at 11:05, Andy Nichols andy.nich...@theqtcompany.com wrote: On 14 Jul 2015, at 16:37, Robin Burchell robin...@viroteck.net wrote: Hi, I would like to nominate plfiorini for Approver status. Would anyone like to second? +1 from me as well Another +1 from me too. Cheers,

Re: [Development] Qt LTS C++11 plans

What they did was to move registration of meta object content to runtime. They basically have structs with static variables and they rely on initialization of these variables at program start-up. It's a lot of macro magic and relies on things like __LINE__ to create unique tokens. The info

Re: [Development] Specifying module dependencies

To the CI system the optional dependencies are also required ones. So we're not going to test the optionality of said dependencies? Louai -Original Message- From: development-bounces+louai.al-khanji=theqtcompany.com@qt- project.org [mailto:development-bounces+louai.al-

Re: [Development] QtCS: Long Term Release discussion

So this bit in the article is not factual? Windows Embedded Compact no longer provides its own tool chain (compiler, assembler, and make), but instead use the same tools as desktop development. Louai -Original Message- From: development-bounces+louai.al-khanji=theqtcompany.com@qt-

Re: [Development] New Module for Serial Buses

I guess I was expecting something higher-level... :) One step at a time. :) Louai ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QTextStream::readLine(0) is an ambiguous overload in 5.5

-Original Message- From: development-bounces+louai.al-khanji=theqtcompany.com@qt- project.org [mailto:development-bounces+louai.al- khanji=theqtcompany@qt-project.org] On Behalf Of Marc Mutz Sent: Monday, May 18, 2015 2:47 PM To: development@qt-project.org Subject: Re:

Re: [Development] [Interest] Qt XML patterns

I've used it in various projects to massage badly designed XML data into a nicer format using XQuery. It's a shame the module isn't worked on more, sometimes one line of XQuery solves a problem that would take a lot of effort with our XML stream reader. Louai -Original Message-

Re: [Development] QtCore missing check for memory allocation

It's my understanding that on Windows you link the global operator new/delete replacement into every dll separately. A howto: 1) Implement your replacement global operator new and delete. Just do so in a single .cpp file, you don't need a header. 2) Compile this into a static library. 3) Pass

Re: [Development] QtCore missing check for memory allocation

Message- From: Gunnar Roth [mailto:gunnar.r...@gmx.de] Sent: Friday, February 27, 2015 2:11 PM To: Al-Khanji Louai Cc: development@qt-project.org Subject: Aw: Re: [Development] QtCore missing check for memory allocation Hi,  in fact both C++11 and C++14 have improved the ways in which

Re: [Development] QtCore missing check for memory allocation

In that case they cannot be overwritten without a recompile. Which brings me back to my original comment from yesterday (to which no one replied): How is that different from linking a custom implementation of operator new/operator delete and malloc/free into Qt? These are embedded use-cases

Re: [Development] QtCore missing check for memory allocation

How is that different from linking a custom implementation of operator new/operator delete and malloc/free into Qt? These are embedded use-cases anyway, so you wouldn’t be using a stock Qt binary. Implementing the above is well-documented, and in fact both C++11 and C++14 have improved the

Re: [Development] Adding new third party component three.js to Qt?

The thread seems to have derailed quite badly, so let's reboot it and return to the original topic of how to bundle the javascript code. If I understand correctly, there is a desire to be able to provide the modified three.js code as a separate package. We have an existing solution for this,

Re: [Development] Adding new third party component three.js to Qt?

On Wednesday 7. January 2015 06.03.14 Keränen Pasi wrote: Hi, I¹d like to open the discussion on including the three library as part of Qt 5.6 and onwards. Mainly because this would give our users a better experience if we¹d bundle the right, tested version of Three.js together with

Re: [Development] changing Q_GADGET

Out of the box, C++ makes class member declarations private. I quite strongly feel that changing that behavior in a macro is not what the user expects. So for me at least the better API box is not being checked here - I quite regularly declare private variables under Q_OBJECT and have done so

Re: [Development] Nominating Paul Lemire as Approver

Another +1 from me. Sorry for the top post. -- Louai -Original Message- From: development-bounces+louai.al-khanji=theqtcompany.com@qt- project.org [mailto:development-bounces+louai.al- khanji=theqtcompany@qt-project.org] On Behalf Of Milian Wolff Sent: Friday, November 14, 2014

Re: [Development] The dark side of QtMultimedia

Usually, I’d say that should be gstreamer’s job. They should provide unit tests that allow testing a gstreamer implementation on a linux system/board. Agreed, and you'd expect that a decent Linux distribution runs them to be sure that they've installed everything correctly. But we're

Re: [Development] Nominating Louai Al-Khanji as approver

Thanks for the votes of confidence! -- Louai From: development-bounces+louai.al-khanji=theqtcompany@qt-project.org development-bounces+louai.al-khanji=theqtcompany@qt-project.org on behalf of Blasche Alexander alexander.blas...@theqtcompany.com Sent:

Re: [Development] The life of a file name and other possibly mal-encoded strings on non-Windows systems

It's not a platform bug. It's an application/framework (Qt) bug. Unix paths are just a byte array, where certain bytes have special meaning (mostly just '/'). Passing around those byte arrays from/to platform functions will always work correctly. The problem is that Qt tries to interpret