Re: [Development] QtCoap: QNAM-like API or not

[Maurice Kalinowski]

> > They model their Coap client after QNAM and related classes (like
> > QNetworkRequest/Reply pair).
> >
> > As I understand it now - DTLS or not does not affect this API much -
> > they can later
> 
> You don't know that. Until we know how DTLS will work, we won't know if
> there's any impact in the front-end API for CoAP. For example, can you use
> one CoAP server for both encrypted and not encrypted? Multicast and
> unicast?
> 
> What's more, we CANNOT release a full CoAP API until it implements DTLS.
> It's just not acceptable to do so otherwise. Therefore, until there's DTLS, 
> the
> API is Technology Preview and subject to change. So I don't feel we need to
> review it yet. I have not spent any time myself.
> 
[Maurice Kalinowski] 

I guess having it as Technology Preview for a first release is the usual way to 
go anyways. That way, the API could still be changed afterwards, but also 
interested parties could get a first impression and suggest adoptions already, 
even though DTLS is not available yet.

Personally, I do not see those two items (missing DTLS, release TP) 
conflicting. The only "problem" which might exist, if DTLS takes too long to 
implement and CoAP would stay for a very long time in TP mode.

Maurice
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qsqldrivers can't loaded in another PC

[Thiago Macieira]

On Monday, 15 January 2018 14:12:32 PST Bartosz Pajewski wrote:
> I need a little bit help.
> 
>  After compilation my app and include necessary libraries the app has
> problem with load drivers included in plugins/sqldrivers.
> The problem is solved, if I install Qt, and compile project again.
> 
> How connect dynamicly qsqldrivers into app, to solved problem: "Sql:
> Drivers not loaded"?

Please confirm with ldd that the plugin files (the .so files in plugin/
sqldrivers) do not have any "not found" listed.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center



___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QtCoap: QNAM-like API or not

[Thiago Macieira]

On Sunday, 14 January 2018 22:15:15 PST Timur Pocheptsov wrote:
> > I don't think we can make any decisions on CoAP until DTLS support is
> > there. It may influence what the CoAP API looks like.
> 
> Thiago, could you, please, clarify this?

Sure. There's no DTLS API. Therefore, CoAP API cannot be implemented.

> They model their Coap client after QNAM and related classes (like
> QNetworkRequest/Reply pair).
> 
> As I understand it now - DTLS or not does not affect this API much - they
> can later

You don't know that. Until we know how DTLS will work, we won't know if 
there's any impact in the front-end API for CoAP. For example, can you use one 
CoAP server for both encrypted and not encrypted? Multicast and unicast?

What's more, we CANNOT release a full CoAP API until it implements DTLS. It's 
just not acceptable to do so otherwise. Therefore, until there's DTLS, the API 
is Technology Preview and subject to change. So I don't feel we need to review 
it yet. I have not spent any time myself.

> From client side QDtlsConnection I'm working on is not very different
> 
> from QSslSocket/QUdpSocket as we have them in Qt now (though it's none of
> them exactly).

We talked about sharing sockets and everything else. There's a lot that may 
change once you get to the final details.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center



___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] 32bit linux build of qt5.10.0 w/ webengine

[Toan Pham]

Hi all,

I found out what the problem was, as to why qtwebnegineview did not show up
on my embedded target (x86 pentium4).  The problem was that on my embedded
target, I wrote my own version of udev, which did not account for folder
creation of /dev/shm when that event came in over netlink-bus.  By creating
that folder manually (mkdir -p /dev/shm) first, then launch the browser,
everything begin to work as expected.  So this was just a bug on my udev
process.  Cheers!






On Fri, Jan 12, 2018 at 9:54 AM, Toan Pham  wrote:

>
> I am suspecting that the reason why qtwebengineview did not render because
> it could not establish IPC connection to qtwebengineprocess.  As seen in
> the error below, qtwebengineview aborted when it received unexpected number
> of bytes from the IPC initialization call (recvmsg): "unexpected number of
> handles".  The second error is related to QT not able to allocate more
> memory: "FATAL:memory.cc(22)] Out of memory. size=262144".  The system had
> more than 1.8G of RAM, so I do not see how it is possible.
>
>
>
> Reference: Error and stack trace of application:
>
> >> [13118:13122:0112/095238.425618:ERROR:broker_posix.cc(46)] Received
> unexpected number of handles
>
> My assumption here is that qt could not establish IPC connection with
> webengineprocess!
>
>
>
> >> [13118:13122:0112/095238.425832:WARNING:client_shared_bitmap_manager.cc(98)]
> Browser failed to allocate shared memory
> >> [13118:13122:0112/095238.425986:FATAL:memory.cc(22)] Out of memory.
> size=262144
> >> #0 0x412c4f36 
> >> #1 0x412c4c5d 
> >>  #2 0x412d6c4d 
>
> Obviously, bitmap manager could not allocate memory.  The question is
> why?  system had pretty of RAM.
>
>
>
> On Thu, Jan 11, 2018 at 12:49 PM, Toan Pham  wrote:
>
>>
>> Thiago,
>>
>> I managed to get the build completed by performing these steps:
>>
>>   1.  Followed your advise on enabling sse2 because it is a
>> hard-requirement.
>>   2.  Patched libvpx heavily to disable avx+avx2/sse3+ (see attached
>> patch)
>>   3.  Patched libyuv (see attached patch)
>>   4.  Patched qwebengine/src/core/Makefile.gn_run to launch ninja in
>> single thread - otherwise build w/ terminate by Out-Of-Memory manager.
>>   5.  Used 32bit native linker even though you recommended a 64bit linker.
>>
>> Step# 2 and 3 were needed because the compiler I was using was optimized
>> for pentium4, it wouldn't be able to compile/link-in SIMD instructions
>> beyond SSE2.
>>
>>
>> After all that hard work, minimal webengine browser (located at
>> qtwebengine/examples/webengine/minimal) did not show anything when I
>> launched it (see attached screenshot).  I also launched the same browser
>> which worked fine under lxc-ubuntu16.04-32bit; but did not show anything
>> within the chroot environment of the pentium4 build.  OnPageLoad event of
>> qtwebengine showed that webpage loaded successfully; so it made me to
>> believe that this is an issue with qwebenginewidget.  FYI, within the same
>> build environment, I was able to run QtWebKit from Qt-5.x a few months
>> back.  Please help if you know what possibly happened to qwebengineview not
>> rendering anything on the view.
>>
>>
>> Thank you,
>>
>> TP
>>
>>
>>
>>
>> On Mon, Jan 8, 2018 at 3:21 AM, Lars Knoll  wrote:
>>
>>> >
>>> >> For me, it's quite simple:
>>> >> No (opensource/commercial) Qt CI = No (opensource/commercial) Qt
>>> >> binaries = No (opensource/commercial) support.
>>> >
>>> > No CI, see above.
>>> > No binaries, build from sources.
>>> > No support, sorry, I can't comment.
>>>
>>> Just a quick comment from TQtC’s perspective on this: We do commercially
>>> support more platforms than we create binaries for. Linux/32bit is
>>> certainly one of those.
>>>
>>> But as Thiago pointed out, those platforms are not always tested quite
>>> as well (unfortunately we can’t possibly test all combinations of OS/CPU
>>> architecture/distribution in our CI).
>>>
>>> Cheers,
>>> Lars
>>>
>>> >
>>> >> If you don't build and test on a regular basis, it can break at any
>>> >> moment without anyone noticing (and it did happened at least once)
>>> >
>>> > You're right, but given all the other permutations, we're very likely
>>> covered
>>> > at a good 99% certainty.
>>> >
>>> >> PS: In case you think I'm ranting for free here, i would like to say
>>> >> (again) that I think Qt is a great piece of (opensource/commercial)
>>> >> SW, and big thumb up to anyone behind this, The Qt Project, The Qt
>>> >> Company, Intel, ICS, KDAB, KDE, ... and everyone else, individual or
>>> >> corporate.
>>> >
>>> > We're having a constructive conversation, don't worry.
>>> >
>>> > --
>>> > Thiago Macieira - thiago.macieira (AT) intel.com
>>> >  Software Architect - Intel Open Source Technology Center
>>> >
>>> > ___
>>> > Development mailing list
>>> > Development@qt-project.org
>>> > 

[Development] Qsqldrivers can't loaded in another PC

[Bartosz Pajewski]

I need a little bit help.

 After compilation my app and include necessary libraries the app has
problem with load drivers included in plugins/sqldrivers.
The problem is solved, if I install Qt, and compile project again.

How connect dynamicly qsqldrivers into app, to solved problem: "Sql:
Drivers not loaded"?

-- 
Regards
Bartosz Pajewski
www.bartoit.pl
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Repository request: Qt Notifier

[Shawn Rutledge]

> On 15 Jan 2018, at 16:25, Ryan Chu  wrote:
> 
> Hi all,
> 
> I'm working on a task supporting "Push Notification" for Qt applications. 
> This feature will be implemented on Android and iOS devices as the first 
> stage. A new module called "Qt Notify" will be created for all platforms. 
> Therefore I request a repository.

It will need to have multiple backends right from the beginning.

The usual problem on Android is that GCN depends on Google Play Services: it's 
not a built-in Android feature.  So some privacy-respecting free software uses 
polling solutions instead.  But polling solutions tend to drain the battery by 
using the radio too much (so I have had trouble using such apps).  That’s a 
shame (technically) because GCM manages to get all apps’ notifications over a 
single connection, which is idle most of the time and thus about as efficient 
as it can be.

Depending on a third-party library is weird though, I agree…

So maybe we need two backends already on Android.  One using GCN, and one where 
we try to make a polling solution that is good enough to actually use as an 
alternative.

iOS has APNS.  (They pioneered the idea, if memory serves.)

On other platforms we could imagine having alternative backends that use 
standards-based network solutions like XMPP or Matrix (but there are many many 
others to choose from, potentially).  https://puri.sm/shop/librem-5/ will use 
Matrix, so maybe we should help them support the same API that we come up with, 
so that Qt apps will be portable to that platform too, when it comes out.  
(They’ve already said they want to support Qt on it.)

Personally I’m interested in trying to use LoRaWAN for such purposes.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Repository request: Qt Notifier

[Jake Petroules]

“Qt Notifications” (qtnotifications) would be more grammatically in line with 
the rest of our repository names.

--
Jake Petroules - jake.petrou...@qt.io
The Qt Company - Silicon Valley
Qbs build tool evangelist - qbs.io

From: Development  on 
behalf of Ryan Chu 
Sent: Monday, January 15, 2018 4:25:20 PM
To: development@qt-project.org
Subject: [Development] Repository request: Qt Notifier

Hi all,

I'm working on a task supporting "Push Notification" for Qt applications. This 
feature will be implemented on Android and iOS devices as the first stage. A 
new module called "Qt Notify" will be created for all platforms. Therefore I 
request a repository.

The first draft of this work was implemented in QtAndroidExtra 
https://codereview.qt-project.org/#/c/216407/. That would have added its 
3rdparty libraries to every application, even if this feature is not used. A 
standalone module makes it possible for users to include or exclude this 
feature.

Name of the project: Qt Notify
Responsible person: Ryan Chu
Gerrit user/email: ryan@qt.io
Desired repository name: qtnotify

Best regards,
Ryan Chu

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Adam Treat for approver

[Lars Knoll]

I agree. Another +1 from me :)

Cheers,
Lars

On 15 Jan 2018, at 14:54, Jake Petroules 
> wrote:

Adam is one of our best. Obvious +1.

--
Jake Petroules - jake.petrou...@qt.io
The Qt Company - Silicon Valley
Qbs build tool evangelist - qbs.io

From: Development 
>
 on behalf of Simon Hausmann >
Sent: Monday, January 15, 2018 2:52:29 PM
To: development@qt-project.org
Subject: [Development] Nominating Adam Treat for approver

Hi,

I would like to nominate Adam for approver status. He has been developing with 
Qt for more than a decade and has been working on Qt and Qt 3D studio full time 
for about a year. I fully trust him to review changes thoroughly and reject 
stuff that looks fishy :)



Simon
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Repository request: Qt Notifier

[Ryan Chu]

Hi all,

I'm working on a task supporting "Push Notification" for Qt applications. This 
feature will be implemented on Android and iOS devices as the first stage. A 
new module called "Qt Notify" will be created for all platforms. Therefore I 
request a repository.

The first draft of this work was implemented in QtAndroidExtra 
https://codereview.qt-project.org/#/c/216407/. That would have added its 
3rdparty libraries to every application, even if this feature is not used. A 
standalone module makes it possible for users to include or exclude this 
feature.

Name of the project: Qt Notify
Responsible person: Ryan Chu
Gerrit user/email: ryan@qt.io
Desired repository name: qtnotify

Best regards,
Ryan Chu

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Mismatch of display resolutions and window sizes in Android applications

[Denis Shienkov]

Hi,

> This is by design for Qt::AA_EnableHighDpiScaling: you get the logical
window size.

Yes, seems it is. I did not know that. Now, I do not use
Qt::AA_EnableHighDpiScaling
at all, because I need to operate with a real resolutions.

Many thanks, anyway. :)

2018-01-15 17:12 GMT+03:00 Morten Sørvig :

> This is by design for Qt::AA_EnableHighDpiScaling: you get the logical
> window size. The
> physical size can be computed by multiplying with QQuickWindow::
> effectiveDevicePixelRatio().
>
> For QtLocation it looks like you have to enable high-dpi tiles by setting
> “osm.mapping.highdpi_tiles"
> (or a similar option, depending on which tile provider you are using).
>
> Morten
>
>
> > On 13 Jan 2018, at 19:27, Denis Shienkov 
> wrote:
> >
> > The problem was in Qt::AA_EnableHighDpiScaling option.
> >
> > 13.01.2018 19:34, Denis Shienkov пишет:
> >> Hi all.
> >>
> >> Rigth now I faced with the strange issue is that the QML
> >> window size (screen) does not correspond to the display
> >> resolution.
> >>
> >> For example, I have the "ASUS ZenFone 4 Max ZC554KL"
> >> smartphone which has display resolution as 1280x720 pixels.
> >>
> >> But if I run there the QML application and try to print out
> >> the ApplicationWindow size, then it is 360x568 or 640x288
> >> pixels, depends on orientation. O_o
> >>
> >> I have checked the same and on other smartphones, and see
> >> that there the situation is similar. E.g. for the
> >> "Samsung Galaxy Ace 3 GT-S7270" with 800x480 display I got
> >> 320x460 or 533x247 pixels of my ApplicationWindow.
> >>
> >> For example if try to use the QtLocation module, then any
> >> maps looks ugly.
> >>
> >> It is very bad surprise for me... Because, seems, now I can
> >> not write any applications with high resolusion (or, at least
> >> to operate with a real resolutions from my QML code).
> >>
> >> Is there are any tricks to fix it?
> >>
> >> PS: Some Android's firmwares (e.g. Cyanogen)  allows to change
> >> the DPI, and with the minimum DPI the ApplicationWindow size
> >> increases a bit.. But it is not an option anyway.
> >>
> >> BR,
> >> Denis
> >
> > ___
> > Development mailing list
> > Development@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Mismatch of display resolutions and window sizes in Android applications

[Morten Sørvig]

This is by design for Qt::AA_EnableHighDpiScaling: you get the logical window 
size. The 
physical size can be computed by multiplying with 
QQuickWindow::effectiveDevicePixelRatio().

For QtLocation it looks like you have to enable high-dpi tiles by setting 
“osm.mapping.highdpi_tiles"
(or a similar option, depending on which tile provider you are using).

Morten


> On 13 Jan 2018, at 19:27, Denis Shienkov  wrote:
> 
> The problem was in Qt::AA_EnableHighDpiScaling option.
> 
> 13.01.2018 19:34, Denis Shienkov пишет:
>> Hi all.
>> 
>> Rigth now I faced with the strange issue is that the QML 
>> window size (screen) does not correspond to the display 
>> resolution.
>> 
>> For example, I have the "ASUS ZenFone 4 Max ZC554KL" 
>> smartphone which has display resolution as 1280x720 pixels.
>> 
>> But if I run there the QML application and try to print out
>> the ApplicationWindow size, then it is 360x568 or 640x288
>> pixels, depends on orientation. O_o
>> 
>> I have checked the same and on other smartphones, and see
>> that there the situation is similar. E.g. for the 
>> "Samsung Galaxy Ace 3 GT-S7270" with 800x480 display I got
>> 320x460 or 533x247 pixels of my ApplicationWindow. 
>> 
>> For example if try to use the QtLocation module, then any
>> maps looks ugly. 
>> 
>> It is very bad surprise for me... Because, seems, now I can
>> not write any applications with high resolusion (or, at least
>> to operate with a real resolutions from my QML code).
>> 
>> Is there are any tricks to fix it?
>> 
>> PS: Some Android's firmwares (e.g. Cyanogen)  allows to change
>> the DPI, and with the minimum DPI the ApplicationWindow size
>> increases a bit.. But it is not an option anyway.
>> 
>> BR,
>> Denis
> 
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Adam Treat for approver

[Jake Petroules]

Adam is one of our best. Obvious +1.

--
Jake Petroules - jake.petrou...@qt.io
The Qt Company - Silicon Valley
Qbs build tool evangelist - qbs.io

From: Development  on 
behalf of Simon Hausmann 
Sent: Monday, January 15, 2018 2:52:29 PM
To: development@qt-project.org
Subject: [Development] Nominating Adam Treat for approver


Hi,


I would like to nominate Adam for approver status. He has been developing with 
Qt for more than a decade and has been working on Qt and Qt 3D studio full time 
for about a year. I fully trust him to review changes thoroughly and reject 
stuff that looks fishy :)




Simon
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Nominating Adam Treat for approver

[Simon Hausmann]

Hi,


I would like to nominate Adam for approver status. He has been developing with 
Qt for more than a decade and has been working on Qt and Qt 3D studio full time 
for about a year. I fully trust him to review changes thoroughly and reject 
stuff that looks fishy :)




Simon
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Nominating Joni Poikelin for Approver status

[Andy Shaw]

Hi,

I would like to nominate Joni Poikelin for Approver status. He joined The Qt 
Company over 3 years ago and has consistently contributed to Qt across many 
modules, fixing a number of issues here and there. His Gerrit dashboard is here:

https://codereview.qt-project.org/#/q/owner:%22Joni+Poikelin+%253Cjoni.poikelin%2540qt.io%253E%22+status:merged,n,z

Disclaimer: We both work in the same team (support) inside The Qt Company.

Andy


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Maintainers of qt3dstudio/qt3dstudio

[Pasi Keränen]

Hi,

As the required 15 work days have (ages ago) passed the nominations below for 
Qt 3D Studio are final.
Congratulations to all appointed maintainers!
Thank you Lars for updating the https://wiki.qt.io/Maintainers page and gerrit 
maintainers group.

Regards,
Pasi


From: Development  on 
behalf of Pasi Keränen 
Date: Thursday, 2 November 2017 at 13.49
To: "development@qt-project.org" 
Subject: [Development] Nominating Maintainers of qt3dstudio/qt3dstudio

Hi all,

Those of you who have been following our blog posts or who went to QtCon this 
year know about the new 3D UI design tool and runtime combination we received 
as contribution from NVIDIA earlier this year. The tool is now known as Qt 3D 
Studio and the repositories were opened before Qt WS 2017. For more info check 
out: 
http://blog.qt.io/blog/2017/10/11/qt-3d-studio-source-code-pre-release-snapshots-available/

I’d like to name myself (Pasi Keränen) as the maintainer of Qt 3D Studio. I’ve 
been involved in the project since the early negotiations with NVIDIA and 
handling the receiving of the contribution from them. All the way to leading 
the Qt integration work that is still ongoing towards 1.0 release later this 
month.

As Qt 3D Studio is a large piece of work I’d like to also suggest the following 
persons as maintainers of sub-areas of Qt 3D Studio:
Soili Väinämö – Maintainer of UX, ensuring the user experience of the tool and 
runtime develop going onwards. Soili has been doing excellent work in both 
converting the look’n’feel of the application to leading UX studies on how to 
improve the usability of the product from end user point of view.
Tomi Korpipää – Maintainer of Editor Application code. Tomi has done great work 
in handling the bug flow and converting the look’n’feel to more Qt like 
together with Soili.
Antti Määttä – Maintainer of Runtime 1.0 and runtime integration. Antti has 
long history of working with 3D engine code and has done excellent work in for 
example prototyping OpenGL ES 2 support in the runtime component of Qt 3D 
Studio.
Laszlo Agocs – Maintainer of Qt 3D based Runtime 2.0. Laszlo has been working 
on the prototype runtime for some time now and is already looking in to 
productizing it.
Miikka Heikkinen – Maintainer of installer and viewer application. Miikka has 
been instrumental in getting the installer creation implemented and also has 
been adding new experimental features to the viewer like image sequence 
generation.

Regards,
Pasi Keränen
Team lead of TQtC 3D Team, Oulu
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development