On 31 Aug 2018, at 02:06, Chris Adams
mailto:chris.ad...@qinetic.com.au>> wrote:
Hi Eddy,
I'm willing to be listed as the maintainer of QtFeedback for now. If
it ever gets more development attention and released as a supported
module then someone with more time to give should probably take ove
Hi Eddy,
I'm willing to be listed as the maintainer of QtFeedback for now. If
it ever gets more development attention and released as a supported
module then someone with more time to give should probably take over,
but until then I'm more than happy to review any changes people might
contribute
On Thursday, 30 August 2018 08:46:32 PDT Uwe Rathmann wrote:
> On Thu, 30 Aug 2018 07:50:41 -0700, Thiago Macieira wrote:
> > The result of (b) is a retained-mode scene graph. It's in the QtQuick
> > library.
>
> I know, but now we have Qt 5.11 and it is fair to review this result:
>
> the API of
El dijous, 30 d’agost de 2018, a les 20:42:11 CEST, Albert Astals Cid via
Development va escriure:
> Unfortunately I have not been able to compile with the memory sanitizer
> enabled yet.
Done :)
https://github.com/albert-astals-cid-kdab/oss-fuzz/commit/b4f28e7dc5e4b936166cda1be36c3bde6b62c53d
El dijous, 30 d’agost de 2018, a les 8:59:40 CEST, André Pönitz va escriure:
> On Thu, Aug 30, 2018 at 08:42:11PM +0200, Albert Astals Cid via
>
> Development wrote:
> > I made a local test run of the undefined sanitizer and it found
> > https://paste.kde.org/prkox41mx in a few seconds, so "it wor
Hi Albert,
Nice! Robert has been working on exactly the same thing lately. I think it
would be good if you guys coordinated the effort :)
It would be ideal, if we could somehow get those mails forwarded to the
security mailing list. I wonder whether we could do that with a special mail
account
On Thu, Aug 30, 2018 at 08:42:11PM +0200, Albert Astals Cid via
Development wrote:
> I made a local test run of the undefined sanitizer and it found
> https://paste.kde.org/prkox41mx in a few seconds, so "it works"
>
> If you want to test it locally you can do python infra/helper.py
> build_fuzzer
oss-fuzz is an online fuzzing service run by Google.
They test daily the code base and run fuzzying over it, maintaining a list of
open and closed bugs.
As example you can see one of the poppler issues i fixed at
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9382
Everything is don
On Thu, 30 Aug 2018 07:50:41 -0700, Thiago Macieira wrote:
> The result of (b) is a retained-mode scene graph. It's in the QtQuick
> library.
I know, but now we have Qt 5.11 and it is fair to review this result:
the API of the scene graph - as it is today - is so far from offering a
comparable
On onsdag 29. august 2018 20.17.52 CEST Robert Löhning wrote:
> Am 22.08.2018 um 10:53 schrieb Frederik Gladhorn:
> > Quick status update from my side:
> > I have the script running against a test installation of JIRA. It seems to
> > work, there are some small issues to be worked out still.
> >
>
On Thursday, 30 August 2018 06:09:22 PDT Uwe Rathmann wrote:
> Furthermore nobody seems to be interested in working on the OpenGL paint
> engine
That paint engine was always experimental and the experiment concluded. There
were two important conclusions:
a) retrofitting paint events on top of Op
On Thu, 30 Aug 2018 14:26:34 +0300, Denis Shienkov wrote:
> Yeah, seems that Qt5 && X11 && 'xcb' backend with the Qwt 6.2 and
> QwtPlotOpenGLCanvas does help a bit. The iMX6 CPU usage now is ~50%
> (instead of previous 100%).
A small correction for others reading this: trunk is Qwt 6.3. The main
I notice, as part of seeking folk to look at API reviews, that we have
several modules with no Maintainer: qtandroidextras, qtgraphicaleffects,
qtmacextras, qtquick1, qtquickcontrols, qtsvg, qtwinextras and (the one
that brought this to my attention) qtxmlpatterns, according to [0].
* [0] https://
On Thu, 30 Aug 2018 14:26:34 +0300, Denis Shienkov wrote:
> Yeah, seems that Qt5 && X11 && 'xcb' backend with the Qwt 6.2 and
> QwtPlotOpenGLCanvas does help a bit. The iMX6 CPU usage now is ~50%
> (instead of previous 100%).
I have been attending one of the Qt roadshows last year in Munich. One
Hi Uwe,
many thanks for your help! :)
Yeah, seems that Qt5 && X11 && 'xcb' backend with the Qwt 6.2 and
QwtPlotOpenGLCanvas
does help a bit. The iMX6 CPU usage now is ~50% (instead of previous 100%).
PS: But compilation for latest Qwt version from trunk r2921 fails, please
look on this my post:
> On 29 Aug 2018, at 20:17, Robert Löhning wrote:
>
> Am 22.08.2018 um 10:53 schrieb Frederik Gladhorn:
>> Quick status update from my side:
>> I have the script running against a test installation of JIRA. It seems to
>> work, there are some small issues to be worked out still.
>>
>> - Qt Cre
On Wed, 29 Aug 2018 16:43:40 +0300, Denis Shienkov wrote:
> So, there are no way to improve an acceleration and to minimize the CPU
> loading?
It depends on the requirements of your application, but when it comes to
oscilloscope alike widgets your best choice is Qt4/X11.
The X11 paint engine is
17 matches
Mail list logo
