Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

On 07/13/2017 12:13 AM, Thiago Macieira wrote: Third, only 1.8 times faster? That's actually a very impressive JIT. I'd have expected a much worse number. Yes but the longer the loop lasts in the example, the greater the difference is between the executable and Node.JS. The "speed slope" is

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

On quarta-feira, 12 de julho de 2017 20:54:54 PDT Phil Bouchard wrote: > On 07/12/2017 10:28 PM, Thiago Macieira wrote: > > On quarta-feira, 12 de julho de 2017 12:34:35 PDT Phil Bouchard wrote: > >> I don't know about you but a minimalist version of g++ embedded inside > >> the > >> browser could

[Development] A taste of the future: declaring QLists without <>

Hi, reading about the new C++17 standard, I decided to test some Qt code: ... QList li = {7,8,4,2,5,4,3}; QList ll = {5,3,34,5,44}; qDebug() << li; qDebug() << ll; ... The normal g++ 5.4 on vanilla Qt 5.9.1 on my Ubuntu 16.04 returns: "home/henry/test/mainwindow.cpp:13: error: missing template

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

On 07/12/2017 07:25 PM, Phil Bouchard wrote: On 07/12/2017 04:56 PM, Konstantin Tokarev wrote: Now add time of compilation to the sum So I just did benchmark the following C++ file featuring a loop within the code (the loop was at the bash shell level previously):

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

On 07/12/2017 10:58 AM, Phil Bouchard wrote: Phil Bouchard wrote: On 07/11/2017 04:02 AM, Tim Blechmann wrote: On the other hand, I have good news as I think I have found a way to simulate functions that return a function. how to you cope with structures like:

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

On 07/12/2017 04:56 PM, Konstantin Tokarev wrote: 12.07.2017, 22:35, "Phil Bouchard" : Phil Bouchard wrote: On 07/11/2017 06:36 AM, Konstantin Tokarev wrote: 10.07.2017, 21:56, "Phil Bouchard" : Phil Bouchard

[Development] Qt-AES - Looking for comments

>From: Thiago Macieira >Date: Wed, 12 Jul 2017 10:59:30 -0700 >Subject: Re: [Development] Qt-AES - Looking for comments >On quarta-feira, 12 de julho de 2017 09:40:17 PDT Matteo wrote: >> >>you do, what value does your library have on top of the 4 processor >>

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

12.07.2017, 22:35, "Phil Bouchard" : > Phil Bouchard wrote: >>  On 07/11/2017 06:36 AM, Konstantin Tokarev wrote: >>>  10.07.2017, 21:56, "Phil Bouchard" :  Phil Bouchard wrote: >  BTW converting

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

Phil Bouchard wrote: > On 07/11/2017 06:36 AM, Konstantin Tokarev wrote: >> >> >> 10.07.2017, 21:56, "Phil Bouchard" : >>> Phil Bouchard wrote: BTW converting Javascript into C++ seems very easy to do >>> >>> In fact, is

Re: [Development] Qt-AES - Looking for comments

On quarta-feira, 12 de julho de 2017 09:40:17 PDT Matteo wrote: > >>you do, what value does your library have on top of the 4 processor > >>instructions? > > You mean using the AES-NI instructions? Yes, for x86. I think ARM has them too. > The tinycrypt project you show me does not look like

Re: [Development] Qt-AES - Looking for comments

12.07.2017, 19:36, "Thiago Macieira" : > On quarta-feira, 12 de julho de 2017 09:26:52 PDT Konstantin Tokarev wrote: >>  12.07.2017, 19:21, "Thiago Macieira" : >>  > On quarta-feira, 12 de julho de 2017 07:52:20 PDT Matteo wrote: >>  >> At

[Development] Qt-AES - Looking for comments

>From: Thiago Macieira >To: development@qt-project.org >Date: Wed, 12 Jul 2017 09:20:26 -0700 >Subject: Re: [Development] Qt-AES - Looking for comments >On quarta-feira, 12 de julho de 2017 07:52:20 PDT Matteo wrote: >> At the beginning this was for my own personal use

Re: [Development] Qt-AES - Looking for comments

On quarta-feira, 12 de julho de 2017 09:26:52 PDT Konstantin Tokarev wrote: > 12.07.2017, 19:21, "Thiago Macieira" : > > On quarta-feira, 12 de julho de 2017 07:52:20 PDT Matteo wrote: > >> At the beginning this was for my own personal use as I was in need of > >> some

Re: [Development] Qt-AES - Looking for comments

12.07.2017, 19:21, "Thiago Macieira" : > On quarta-feira, 12 de julho de 2017 07:52:20 PDT Matteo wrote: >>  At the beginning this was for my own personal use as I was in need of some >>  sort of encryption for a work project without using openssl, then I just >>  

Re: [Development] Drag and Drop Issue in Qt-5.3.2 with QML on QNX Platform only.

On quarta-feira, 12 de julho de 2017 09:15:15 PDT Prashant Purohit wrote: > We are using QT 5.3.2 with QML on QNX. > > The point to note here is that when we tried same code on Linux > machine with QT-5.3.2, this issue does not occur. > > Is there any fix done for QT-QML-QNX related to this

Re: [Development] Qt-AES - Looking for comments

On quarta-feira, 12 de julho de 2017 07:52:20 PDT Matteo wrote: > At the beginning this was for my own personal use as I was in need of some > sort of encryption for a work project without using openssl, then I just > released the code for the class on github, it's more a code exercise than a >

[Development] Drag and Drop Issue in Qt-5.3.2 with QML on QNX Platform only.

Hi All, We have created one application where there are multiple icons present in a GridView. Each delegate of the grid is a composite control with an icon and text. (This is similar to phone apps screen on Android/iOS devices). Similar to apps screen on mobile devices, user can drag and drop

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

Phil Bouchard wrote: > On 07/11/2017 04:02 AM, Tim Blechmann wrote: >>> On the other hand, I have good news as I think I have found a way to >>> simulate functions that return a function. >> >> how to you cope with structures like: >> >> function foo( outObject ) >> { >>

Re: [Development] Qt-AES - Looking for comments

At the beginning this was for my own personal use as I was in need of some sort of encryption for a work project without using openssl, then I just released the code for the class on github, it's more a code exercise than a real usable class for the issues you pointed out. On Wed, Jul 12, 2017 at

Re: [Development] Qt-AES - Looking for comments

On quarta-feira, 12 de julho de 2017 04:43:48 PDT Marc Mutz wrote: > On 2017-07-12 00:05, Matteo wrote: > [...] > > > My point was not to use openssl or external libs, i understand the > > security issue of something that is not certified and audited. > > [...] > > Good to know. Now you "just"

Re: [Development] Qt-AES - Looking for comments

On 2017-07-12 00:05, Matteo wrote: [...] My point was not to use openssl or external libs, i understand the security issue of something that is not certified and audited. [...] Good to know. Now you "just" need to make sure *all* your potential users understand this, too. Which brings me to

Re: [Development] QT 5.9. Issues with QWebEngine

Hi Kai, Thanks for your prompt response. Before loading any URL In QWebEngine, I am making it use System Proxy Configuration by following code; QNetworkProxyFactory::setUseSystemConfiguration(true); After this if I query the proxy, I get correct proxy address which is configured in Web

Re: [Development] QT 5.9. Issues with QWebEngine

Hi Sudhir, This is best discussed on bugreports.qt.io, in a bug report for component "WebEngine" in project "Qt". Please include on how you want to set a (non-local) proxy: - through the system settings or - through QNetworkProxy::applicationProxy Regards Kai > -Original Message- >

[Development] QT 5.9. Issues with QWebEngine

HI, QWebEngine does not take exact proxy settings from System (as done in internet browsers like Chrome) Internet client is configured to use proxy for internet addresses and bypass it for local addresses. But it does not happen. QWebEngine fails to bypass proxy for local urls. Scenarios: -

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

Le 11/07/2017 à 13:49, Phil Bouchard a écrit : On 07/11/2017 04:02 AM, Tim Blechmann wrote: On the other hand, I have good news as I think I have found a way to simulate functions that return a function. how to you cope with structures like: function foo( outObject ) { var object = {}